BSheets MCP tool compatibility

The MCP server advertises canonical BSheets tool names. Calls using the legacy names in the table below are translated only for server release 1.0.1. Update agents and integrations before upgrading to 1.0.2.

Legacy call name	Canonical name
`list_native_sheets`	`list_bsheets`
`get_native_sheet`	`get_bsheet`
`create_native_sheet`	`create_bsheet`
`delete_native_sheet`	`delete_bsheet`
`duplicate_native_sheet_as_input`	`duplicate_bsheet_as_input`
`format_native_sheet`	`format_bsheet`
`edit_native_sheet_tab`	`edit_bsheet_tab`
`delete_native_sheet_row_column`	`delete_bsheet_row_column`
`recalculate_native_sheet`	`recalculate_bsheet`
`create_output_sheet_view`	`create_bsheet_output_view`
`refresh_output_sheet_view`	`refresh_bsheet_output_view`
`write_native_sheet_cells`	`update_bsheet_cells`
`render_native_sheet_cell_explanation`	`explain_bsheet_cell`

Aliases translate before permission checks and auditing, so both names reach the same handler and idempotency path. Only canonical names appear in tool discovery, search, MCP Apps allowlists, and generated directory contracts. discard_staged_edit remains a hidden direct recovery call; it is not a discoverable tool or an editor action.

update_bsheet_cells commits through the automatic save and calculation workflow. Its canonical input schema has no staging mode. recalculate_bsheet is an explicit programmatic formula-repair API, not an editor action. Explain remains a user message or prompt; the agent calls explain_bsheet_cell, which returns the dedicated cell-explanation App.

Tool aliases do not change persisted .btsheet.json or .bsheet.json files, stored sheet data, or historical snapshots.

App and schema resource aliases

Current App resources are ui://apps/bsheet-editor, ui://apps/bsheet-viewer, and ui://apps/bsheet-cell-explain. Reads of the previous ui://apps/native-sheet-* identities resolve to the matching current, content-addressed bundle. The schema and examples are published at bridge-town://bsheets/schema/v1 and bridge-town://bsheets/examples/*; reads of their former bridge-town://native-sheets/* URIs resolve to the canonical resources.

New REST clients use /api/models/{model}/bsheets. Existing /api/models/{model}/sheets requests remain supported with the same methods, authorization, SHA checks, and write receipts.