Skip to main content
Glama

Get my booking

get_my_booking
Read-onlyIdempotent

Get one of the signed-in client's bookings, with guide contact and refund estimate.

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

Input Schema

NameRequiredDescriptionDefault
booking_idYes

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 declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: the result includes guide contact details and a refund estimate, which tells the agent what it will get back. It stays short of a 5 because it omits what happens for a booking the caller does not own (error vs. empty).

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 well-formed sentence with no filler; the scope constraint ('signed-in client's') and the payload summary are both front-loaded.

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 one-parameter read with annotations covering safety and no output schema, the description tells the agent what it retrieves and what the response contains. The remaining gap is the ownership/error behavior for an unauthorized booking_id.

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 0%, and the description never mentions booking_id, its UUID format, or that it must reference one of the caller's own bookings. The parameter is self-descriptive by name and the schema carries type/format/required, so this is not harmful, but nothing is added beyond the schema.

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?

States a specific verb and resource: 'Get one of the signed-in client's bookings.' The singular 'one of' implicitly contrasts with the plural sibling list_my_bookings, and naming the returned payload (guide contact, refund estimate) sharpens the intent. It does not explicitly name a sibling it is not, so it stays at 4 rather than 5.

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: fetch an individual booking belonging to the caller. There is no guidance on when to prefer this over list_my_bookings or cancel_my_booking/request_booking_change, and no note that the ID must belong to the signed-in client.

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