Skip to main content
Glama

Airsockfly

Read booking

get_booking
Read-onlyIdempotent

Read one order with its bookings, insurance policies, vouchers and invoice reference.

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

Input Schema

NameRequiredDescriptionDefault
orderIdYesOrder identifier from list_bookings or create_booking.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, closed-world), so the bar is lower, and the description adds real value by disclosing what the read composes: bookings, insurance policies, vouchers, and an invoice reference. It stops short of mentioning behavior for a non-existent or inaccessible order, which is the main remaining gap for a read tool with no output schema.

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?

A single front-loaded sentence with no filler; the resource and its contents are stated before any qualification. Nothing could be removed without losing meaning.

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?

With one required parameter, full schema coverage, and no output schema, the description's enumeration of returned sub-resources is the key missing piece and it is supplied. Only not-found or authorization behavior is left unaddressed, which is minor for a read-only 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?

Only one parameter and schema description coverage is 100%, with the schema itself explaining that orderId comes from list_bookings or create_booking. The description adds no syntax, format, or constraint detail beyond what the schema states, so 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?

Specific verb ("Read") plus a precise resource scope ("one order") and an enumeration of the aggregate's parts (bookings, insurance policies, vouchers, invoice reference). It implicitly separates itself from list_bookings by emphasizing a single order, though it never names the sibling it replaces.

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: "one order" suggests a single-record lookup after list_bookings or create_booking, but the description states no when-to-use condition, prerequisites, or alternative tool. The only routing hint lives in the schema's orderId description, not the tool description.

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