Skip to main content
Glama

Check booking status

get_booking_status
Read-onlyIdempotent

Get the current status of a booking made with request_booking (查預約狀態: confirmed, waiting for the business, awaiting online payment, declined, or cancelled), including payment and refund details. Read-only.

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": {
      "business_id": "<business_id>",
      "booking_id": "<booking_id>",
      "status_token": "<status_token>"
    },
    "name": "get_booking_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
booking_idYesbooking_id returned by request_booking
business_idYesbusiness_id from search_businesses
status_tokenYesstatus_token returned once by request_booking

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 readOnlyHint, idempotentHint and destructiveHint=false, so the appended "Read-only" is partly redundant. The description nonetheless earns credit for disclosing real behavior beyond the annotations: the closed set of status outcomes (confirmed, waiting for the business, awaiting online payment, declined, cancelled) and the fact that payment and refund details are included in the result.

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 the status enumeration parenthesized rather than sprawling into its own sentence. No preamble, no restatement of the title, and the trailing "Read-only" is compact despite being partly duplicative.

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 no output schema, the description does the necessary work of sketching the return payload (status, payment and refund details), which is the key gap it needed to cover. It stops short of covering failure modes such as an invalid or expired status_token, so it is strong but not exhaustive for a three-required-parameter 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 description coverage is 100%, with each of the three required parameters documented in-schema including provenance (returned by request_booking / from search_businesses), so the baseline applies. The description adds no extra semantics such as token expiry, format, or what happens on a mismatched business_id/booking_id pair.

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+resource ("Get the current status of a booking") and anchors it to the originating sibling ("made with request_booking"), which immediately disambiguates it from get_booking_link, get_availability, and the mutation siblings. The parenthetical enumeration of the five possible status values further pins down what is being retrieved.

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?

Clearly establishes the usage context: this is the follow-up call for a booking previously created via request_booking. It does not, however, name any alternative or exclusion (e.g. what to do if the status_token was lost, or how get_booking_link differs in scope), leaving the agent to infer those boundaries.

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.