Skip to main content
Glama

Request a booking change

request_booking_change

Ask the guide to change a booking, like a new date or party size. The guide decides.

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>",
      "message": "<message>"
    },
    "name": "request_booking_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYes
booking_idYes
preferred_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false. The description adds the key behavioral fact not in the annotations: the outcome is decided by a third party, so the change is not guaranteed. It omits how the agent learns the result, whether repeated requests stack (non-idempotent), and what state the booking enters while pending.

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 short sentences, front-loaded with the action and followed by the guiding behavior. Tight and readable; the only issue is the inaccurate example rather than verbosity.

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

Completeness2/5

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

For a 3-parameter tool with 0% schema coverage and no output schema, the description leaves too much unexplained: what message should contain, what preferred_date does versus free text, and what happens after the request is sent. The mention of a nonexistent party-size field compounds the gap.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the param burden, and it does not: booking_id and message are never explained. Worse, it advertises "party size" as an example change, but no such parameter exists in the schema, which can mislead an agent into omitting that detail or expecting a dedicated field.

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?

"Ask the guide to change a booking" gives a specific verb (request) and resource (booking), and the framing makes clear this is a request rather than a direct mutation. It does not name a sibling to contrast with (e.g. cancel_my_booking or create_booking), so the differentiation is implicit rather than explicit.

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 implied: use this when you want a booking altered rather than cancelled or recreated. "The guide decides" signals the request might be rejected, which is useful context, but there is no explicit when-not guidance, no mention of the alternative sibling tools, and no prerequisite information.

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