Skip to main content
Glama

QConsul LLC

Check booking payment status

confirm_booking
Read-onlyIdempotent

Report whether a prepared booking is confirmed by payment, still awaiting payment, or expired; it never confirms a booking itself. Once paid, it returns the Meet link, receipt link, a calendar event with ICS and stable UID, and agent instructions; it returns no management link. QConsul also emails the customer the calendar invitation; the agent reports the booking to its customer and deduplicates any calendar entry on the UID.

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": {
      "prepareToken": "<prepareToken>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "confirm_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
prepareTokenYesprepareToken returned by prepare_booking.
idempotencyKeyYesKey chosen by the agent; repeat calls return the same state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations: it enumerates the returned artifacts (Meet link, receipt link, calendar event with ICS and stable UID, agent instructions), states what is deliberately absent (no management link), and discloses the customer email side effect plus the agent's dedupe-on-UID obligation. The only soft spot is that the customer email is described as an external effect from a readOnlyHint tool, but the wording presents it as a consequence of an already-completed payment rather than a mutation triggered by the call, so it reads as disclosure rather than contradiction.

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?

Front-loaded with the core state-reporting purpose, then artifacts, then agent obligations – a sensible order with no filler. It is a dense single sentence chain with semicolons, and the 'QConsul also emails...' clause is slightly buried given it changes agent behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 must describe the return payload, and it does so concretely (links, ICS, UID, instructions, explicitly no management link). For a read-only, two-parameter status check, an agent has everything needed to call it and act on the result.

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%, so both prepareToken's origin and idempotencyKey's repeat-call behavior are already documented in the schema. The description adds no further syntax, format, or length guidance, which is the expected baseline 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 ('Report whether a prepared booking is confirmed by payment, still awaiting payment, or expired') and explicitly negates a plausible misreading ('it never confirms a booking itself'), which separates it from prepare_booking without opening either 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?

The 'prepared booking' framing plus the prepareToken parameter makes the sequencing after prepare_booking clear, and the negation rules out using it to confirm. There is no explicit statement about how often to poll or when to stop retrying beyond the schema's idempotency note.

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