Skip to main content
Glama

Get booking

get_booking
Read-only

Fetch one booking with participants, payment status, and feedback.

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_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
booking_idYes
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered elsewhere. The description's contribution is disclosing that the response bundles participants, payment status, and feedback rather than a bare booking row, but it says nothing about error/not-found behavior or permission requirements.

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 sentence with zero filler, front-loaded with the verb and scope, followed by the payload summary. Every clause earns its place.

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 simple single-record read tool with full annotation coverage and self-describing parameters, this is close to sufficient. The main residual gap is what 'feedback' and 'payment status' concretely contain, which matters slightly more than usual because no output schema exists.

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?

With only two parameters, the schema already documents business_id in full (including the 'optional when this connection covers a single business' condition) and declares booking_id as a uuid. The description adds no meaning beyond the schema for either parameter, so it neither compensates for nor worsens the 50% coverage gap.

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?

"Fetch one booking" pairs a specific verb with a specific resource and constrains scope to a single record, and the trailing clause names the sub-data returned (participants, payment status, feedback). It is clearly distinct from the collection-style siblings like get_attention_bookings, though it never names an alternative explicitly.

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 is the lookup to use when it already holds a booking_id. There is no statement of when to prefer this over get_attention_bookings or get_business_overview, and no note about what happens if the booking is not found.

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