ログイン済みユーザーの予約をキャンセルする。未ログインユーザーはキャンセル不可（ログインしていない場合は start_login を呼び、返されたloginUrlをユーザーに提示してログインを案内すること）。キャンセルする reservationNo は create_reservation（予約登録ツール）のレスポンスで取得した値を使用する。実行前に必ずユーザーにキャンセル対象の予約内容を確認し、最終確認を求めること。
| Name | Required | Description | Default |
|---|---|---|---|
| reservationNo | Yes | キャンセルする予約番号。必須。create_reservation（予約登録ツール）のレスポンスで取得した reservationNo。 |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of disclosing behavior. It mentions the prerequisite of login, the need for confirmation (implying destructive action), and the fallback to start_login. However, it does not explicitly state the irreversible nature of cancellation or any potential side effects beyond the cancellation itself.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise yet complete, with each sentence serving a distinct purpose: stating the action, specifying login requirements, identifying the parameter source, and mandating user confirmation. No redundant information is present.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the tool's purpose, prerequisites, parameter source, and confirmation requirement. However, since there is no output schema, it does not mention what the tool returns (e.g., success/failure, updated reservation status), leaving a minor gap in completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter reservationNo has a description that fully explains its meaning and source (from create_reservation's response), covering 100% of the schema. The description adds value by clarifying the required provenance of the value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool cancels a reservation for a logged-in user, using the verb 'キャンセルする' (cancel) and the specific resource '予約' (reservation). It is distinct from sibling tools like create_reservation and start_login.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit guidance: it notes that unauthenticated users cannot cancel and instructs to call start_login and present the loginUrl. It also specifies that reservationNo should come from create_reservation's response and requires user confirmation before execution.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a unique, clearly defined purpose: login, logout, search, genres, availability, create, and cancel. No two tools overlap in functionality, making selection straightforward.
All tools follow a consistent verb_noun pattern in snake_case (e.g., search_shops, get_availability, create_reservation). This predictable naming makes the API easy to navigate.
Seven tools neatly cover the necessary operations for an online reservation system without redundancy or bloat. The scope is appropriately focused on the core workflow.
The toolkit covers the essential reservation lifecycle: login, search, availability check, create, cancel, and logout. While an update/modify reservation tool is absent, it is not a typical requirement for this type of system, so the coverage is nearly complete.