Skip to main content
Glama

Booking status

get_booking_status
Read-onlyIdempotent

Use this when the person asks whether a held time was confirmed, or where their booking stands now. Pass the holdId hold_booking returned. Returns the status (such as awaiting_client, confirmed, requested, declined, cancelled or moved), the business and service, and the start time. It returns no personal details. Do not use for checking again and again in a loop; ask when the person wants to know.

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": {
      "holdId": "<holdId>"
    },
    "name": "get_booking_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
holdIdYesThe holdId hold_booking answered with.
languageNoThe language to answer in (BCP 47).

Output Schema

NameRequiredDescriptionDefault
refNoThe booking's reference, once there is a booking.
metaYes
startYes
statusYesBefore a confirm, where the held time stands; after one, where the booking stands now. moved: the business changed the start.
heldUntilNo
serviceNameYes
businessNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 context: it returns no personal details, it lists the status vocabulary, and it warns against repeated polling. It does not address what happens for an expired or unknown holdId, which is the one behavioral gap.

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?

Three short sentences, front-loaded with the trigger condition, then the parameter, then the return contents and the anti-polling caveat. Every sentence contributes a distinct piece of information with no filler.

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 an output schema present, the description need not detail return shapes, yet it usefully summarizes status, business, service, and start time. Coverage of the calling workflow and privacy posture is solid; only edge cases like invalid or expired holdIds are left unaddressed for a tool this simple.

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% and the schema already explains holdId as 'the holdId hold_booking answered with', so the description's 'Pass the holdId hold_booking returned' largely repeats structured data. The optional language parameter is not mentioned at all. Baseline 3 is appropriate when the schema carries the load.

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

Purpose5/5

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

States a specific verb and resource ('whether a held time was confirmed, or where their booking stands now') and enumerates the status values returned (awaiting_client, confirmed, requested, declined, cancelled, moved). An agent can distinguish this read-status tool from hold_booking, confirm_booking, and release_hold without opening any schema.

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

Usage Guidelines4/5

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

Gives clear triggering context ('when the person asks whether a held time was confirmed') plus an explicit exclusion against polling in a loop, with the recommended alternative behavior (ask when the person wants to know). It stops short of naming a sibling tool as the alternative for any adjacent case, so it lands just below the top mark.

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