Skip to main content
Glama

Cancel my booking

cancel_my_booking
Destructive

Cancel a booking the client made, refunding per the guide's cancellation policy. Call get_my_booking first, tell the user the refund, and pass expected_refund_cents equal to cancellation_refund_cents once they agree.

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": {
      "booking_id": "<booking_id>",
      "expected_refund_cents": "<expected_refund_cents>"
    },
    "name": "cancel_my_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
booking_idYes
expected_refund_centsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety bar is lower. The description still adds meaningful behavior: the cancellation is governed by the guide's policy, the refund must be communicated to the user first, and consent is required before invoking. It does not describe what happens if the expected refund mismatches or what the call returns.

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

Conciseness4/5

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

Two sentences, front-loaded with the action and its effect, then the procedural instructions. No filler or restated name/title. The second sentence is a dense run-on, but every clause carries operational value.

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

Completeness3/5

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

For a destructive two-parameter mutation with no output schema, the description covers the prerequisites and the guard parameter well. Gaps remain: 'the guide's cancellation policy' is an undefined reference with no pointer to where the policy lives, and neither the response shape nor the failure mode on a refund mismatch is described.

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

Parameters4/5

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

Schema coverage is 0% for two parameters, so the description has to carry the load. It explains that expected_refund_cents is a confirmation guard that must be set to the cancellation_refund_cents value obtained from get_my_booking, which is non-obvious semantics. booking_id's provenance and UUID format are only implied by the prerequisite step.

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?

The description opens with a specific verb and resource ('Cancel a booking the client made') plus the side effect ('refunding per the guide's cancellation policy'), which is enough to separate it from get_my_booking and request_booking_change. It stops short of explicitly naming a sibling as the alternative, so the differentiation is implied by the verb rather than stated.

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?

It gives a concrete prerequisite and sequence: 'Call get_my_booking first, tell the user the refund, and pass expected_refund_cents equal to cancellation_refund_cents once they agree.' That is real when/how guidance an agent could not infer from the schema. It does not say when not to use it (e.g. route to request_booking_change for modifications), so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources