エキテンネット予約

cancel_reservation

ログイン済みユーザーの予約をキャンセルする。未ログインユーザーはキャンセル不可（ログインしていない場合は start_login を呼び、返されたloginUrlをユーザーに提示してログインを案内すること）。キャンセルする reservationNo は create_reservation（予約登録ツール）のレスポンスで取得した値を使用する。実行前に必ずユーザーにキャンセル対象の予約内容を確認し、最終確認を求めること。

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": {
      "reservationNo": "<reservationNo>"
    },
    "name": "cancel_reservation"
  }
}

Input Schema

Name	Required	Description	Default
`reservationNo`	Yes	キャンセルする予約番号。必須。create_reservation（予約登録ツール）のレスポンスで取得した reservationNo。

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026
- addedInput schema / properties / reservationNo / pattern
```
Added value: +"^[TMSR][0-9a-f]{8}[A-Z0-9]{3}$"
```
First observedSep 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the burden well by disclosing authentication requirements, the login fallback, the source of the reservation number, and the required final confirmation. It stops short of describing irreversibility, side effects, or failure behavior for an already-cancelled or invalid reservation.

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

Conciseness5/5

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

The description is four focused sentences, front-loading the purpose before auth guidance, prerequisite sourcing, and confirmation requirements. Every sentence adds operational value.

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?

For a simple one-parameter mutation with no output schema, the description covers the critical operational context: login requirement, alternative login flow, reservationNo source, and confirmation. It is slightly incomplete because it does not describe post-cancellation outcomes or error cases.

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 description coverage is 100%, and the schema already documents reservationNo as required with its source from create_reservation. The description repeats that source but adds no additional syntax or semantic detail beyond the schema.

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

Purpose5/5

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

The description states a specific verb and resource: cancelling a logged-in user's reservation. It also distinguishes the tool from siblings by routing unauthenticated users to start_login and directing agents to create_reservation for the reservation number.

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

Usage Guidelines5/5

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

It explicitly states the login prerequisite, the fallback action when not logged in (call start_login and present loginUrl), where to obtain reservationNo, and the mandatory confirmation step before execution. This gives clear when-to-use and when-not-to-use guidance.

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

All エキテンネット予約 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?