Skip to main content
Glama

Airsockfly

Preview cancellation

preview_cancellation
Read-onlyIdempotent

Show what cancelling a booking would cost: penalty, refund and the deadline for free cancellation.

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": {
      "vertical": "<vertical>",
      "bookingId": "<bookingId>"
    },
    "name": "preview_cancellation"
  }
}

Input Schema

NameRequiredDescriptionDefault
verticalYesService type.
bookingIdYesIdentifier of one booking inside an order, from get_booking.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds the response content (penalty, refund, deadline), which is real value given there is no output schema, but it omits whether figures are guaranteed or estimates and whether the call fails on non-cancellable bookings.

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?

One sentence, front-loaded with the operation, followed by the three concrete outputs. Every clause carries information and there is no filler.

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 two-parameter read-only tool with no output schema, the description covers the important gap by enumerating the returned figures. What remains unstated — error conditions for non-cancellable bookings and whether returned amounts are binding — is modest but would matter to an agent deciding whether to act on the preview.

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 itself documents both `vertical` (with a six-value enum) and `bookingId`, including the pattern and the pointer to get_booking. The description mentions neither parameter, so it adds nothing beyond structured data — baseline 3 applies.

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 uses a specific verb-plus-resource construction ("Show what cancelling a booking would cost") and names the concrete values returned: penalty, refund, and free-cancellation deadline. It implicitly separates itself from the write-side siblings (cancel_booking, request_date_change) by framing the operation as a cost preview, but it never states outright that nothing is cancelled, leaving that differentiation to the tool name and readOnlyHint.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this belongs before a cancel_booking call, and the mention of a "deadline for free cancellation" hints at a decision-support role. There is no explicit when-to-use, when-not-to-use, or named alternative, and no statement about what happens if the booking is non-refundable.

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