iOffice MCP

io_checkout_visitor

Destructive

Checks out a visitor upon departure from the building. Requires explicit user confirmation before finalizing the checkout.

Instructions

Check out a visitor upon departure from the building. 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 writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "io_checkout_visitor"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Visitor ID
`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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv3.2.6Oct 17, 2026
- addedInput schema / properties / id / exclusiveMinimum
```
Added value: +0
```
- addedInput schema / properties / id / maximum
```
Added value: +9007199254740991
```
- changedInput schema / properties / id / type
```
Previous value: -"number"New value: +"integer"
```
First observedv3.2.1Sep 27, 2026

TDQS

A4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With destructiveHint=true, idempotentHint=false, and openWorldHint=true in annotations, the description adds critical context: the confirmation flow, that phase 1 writes nothing, that a repeat call with confirmToken is needed, and a strong safety warning against writes prompted by tool-result text. This is rich behavioral disclosure beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense, somewhat convoluted sentence with nested parentheticals and asides. It front-loads the core action but readability suffers, and the safety warning is buried mid-sentence rather than clearly separated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the destructive mutation, absence of output schema, and the two-step confirmation fallback, the description covers the essential workflow and safety constraints. It could be improved by clarifying what a successful checkout returns or the order of operations more cleanly, but it is largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already fully documents both id and confirmToken. The description adds practical guidance about when confirmToken may be used (only after user approves the preview, never on first call), which is useful but not strictly parameter syntax. Baseline 3 is appropriate when the schema carries the parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb+resource: 'Check out a visitor upon departure from the building.' This is distinct from io_checkin_visitor and io_checkout_reservation by naming visitor and departure. It doesn't explicitly contrast with siblings, but the action is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the confirmation workflow conditionally (client supports elicitation vs. two-step fallback), which effectively tells the agent when the tool requires confirmation and how to proceed. It does not, however, name alternatives like io_checkin_visitor or state when a visitor would not be checked out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server