Skip to main content
Glama

Alina Szaputko — Online Consultation Booking

Verify an AI-agent booking payment and confirmation

get_agent_booking_status
Idempotent

Operational status check. The backend may perform idempotent fulfilment when Stripe confirms payment but webhook delivery is delayed; that can create the appointment Calendar event and send booking notifications. Returns only booking status and appointment date/time, not client contact details, payment credentials, event links or calendar notes. Enabled only when the Preview test gate or Production live-booking gate is explicitly configured. Tell the client the appointment is confirmed only when both paid and confirmed are true.

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": {
      "bookingId": "<bookingId>"
    },
    "name": "get_agent_booking_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

With readOnlyHint=false and idempotentHint=true already supplied, the description still adds the critical non-obvious fact that a "status check" can trigger fulfilment (creating the Calendar event, sending notifications) when Stripe confirms payment but the webhook is delayed. It also discloses the availability gate and enumerates what is deliberately not returned, which is exactly the kind of context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Sentences are dense but each carries distinct information: side effects, return scope, availability gate, and the confirmation rule. The safety-critical side-effect clause is placed early, though the opening "Operational status check" is a weak lead-in for what follows.

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 tool with no output schema, the description covers side effects, return contents and exclusions, environment gating, and the criterion for telling a client the booking is confirmed. The only material omission is anything about the identifier or error/not-found behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter, bookingId, with 0% schema description coverage, and the description never mentions it — no format hint for the bk_ prefix/hex pattern, no statement about what happens with an unknown or malformed id. The agent must read the raw JSON schema pattern to know what to pass.

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?

"Operational status check" plus "Returns only booking status and appointment date/time" makes the verb and the returned resource concrete, and the title anchors it to payment/confirmation verification. The one gap is that the first sentence is abstract and the precise object (a booking identified by bookingId) only emerges from the returns clause.

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 implied rather than stated: it is a polling/verification call gated on Preview test or Production live-booking configuration, and the agent is told to declare confirmation only when both paid and confirmed are true. There is no explicit when-to-use/when-not or comparison against the sibling tools, so the agent must infer its place in the flow.

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