io_update_building
Destructive
Update an existing iOffice building by supplying only the fields to change; user confirmation is required before the write is sent.
Instructions
Update an existing iOffice building. Only provide fields to change. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and makes NO network call, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Building ID | |
| city | No | City | |
| name | No | Building name | |
| phone | No | Building phone number | |
| state | No | State or province | |
| country | No | Country code | |
| address1 | No | Street address line 1 | |
| address2 | No | Street address line 2 | |
| postalCode | No | Postal/ZIP code | |
| description | No | Building description | |
| confirmToken | No | ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation. | |
| totalSquareFootage | No | Total square footage |