Skip to main content
Glama

Look up a booking

get_booking
Read-only

A booking, from the private change-or-cancel link in its confirmation email.

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": {
      "link": "<link>"
    },
    "name": "get_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesThe private change-or-cancel link from the customer's confirmation email (or from request_booking).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe-read profile is covered. The description contributes the notable behavioral fact that access is gated by possessing a private link from the confirmation email, i.e. link-as-credential authorization. It does not mention what happens with an expired or already-used link, or whether it returns the booked slot details.

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

Conciseness3/5

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

It is a single short fragment with no wasted words, but brevity here shades into under-specification: there is no verb and no complete sentence, so the reader must reconstruct the action from the name. Structure is front-loaded but grammatically incomplete.

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 one-parameter, read-only lookup with full schema coverage and no output schema, little is strictly required. Still, an agent cannot tell from the description whether a stale or foreign link produces an error, or what fields of the booking come back, which matters for a link-gated lookup.

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 coverage is 100% for the single parameter, and the schema description already explains that the link comes from the confirmation email or from request_booking. The description largely restates that same fact, adding only the word "private" as emphasis, so baseline 3 applies.

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

Purpose3/5

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

The description is a noun phrase ("A booking, from the private change-or-cancel link in its confirmation email") rather than a verb+resource statement, so the action is carried mainly by the name and title. It does add the defining lookup key (the private link), which distinguishes it from list-style or search siblings, but it never says explicitly that it retrieves a booking record.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative among the siblings (get_quote, cancel_booking, change_booking_time). Use is only implied by the phrase "private change-or-cancel link," which suggests the caller must already hold such a link.

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