AdvocateMCP

Confirm Booking

confirm_booking

Destructive

Confirm a reservation made with reserve_slot. Present the returned stored booking_details to the customer and relay only the customer-supplied 6-digit code received at their email or phone; never generate, guess, or fetch it. For an active configured calendar, a verified code attempts a direct commit to the selected calendar with no owner approval. booking_pending means the provider outcome is uncertain; repeat confirm_booking later to check the stored outcome, but it never retries a provider write automatically. A paid booking (reserve_slot returned payment.required = true) has no code: this answers payment_required — pay it with create_booking_payment_link — or payment_in_flight while its payment is settling.

Input Schema

TableJSON Schema

Name	Required	Description
`code`	Yes	The customer-supplied 6-digit confirmation code received at their own email or SMS contact. Relay only that supplied code; never generate, guess, or fetch it.
`slug`	Yes	Business slug identifier
`reservation_id`	Yes	The reservation id returned by reserve_slot

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes	'confirmed': a booking was committed to the selected configured calendar, or a historical legacy reservation was confirmed. 'booking_pending': the provider outcome is unresolved; do not create another booking or seek owner approval — repeat confirm_booking later to read the stored outcome. 'pending_merchant': a historical merchant-review reservation awaits a business decision — see message. 'already_confirmed': this reservation was confirmed earlier (safe replay).
`message`	No	Optional customer-facing status detail to relay
`reservation_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 5, 2026

changedInput schema / properties / code / description

Previous value: -"The 6-digit confirmation code the customer received at their contact (email or SMS) and read back to the agent"New value: +"The customer-supplied 6-digit confirmation code received at their own email or SMS contact. Relay only that supplied code; never generate, guess, or fetch it."

changedOutput schema / properties / message / description

Previous value: -"Present with pending_merchant: customer-facing text to relay"New value: +"Optional customer-facing status detail to relay"

changedOutput schema / properties / status / description

Previous value: -"'confirmed': the code was right and the slot is now exclusively held. 'pending_merchant': the code was right; the business must accept within 24 hours and may decline — see message. 'already_confirmed': this reservation was confirmed earlier (safe replay)."New value: +"'confirmed': a booking was committed to the selected configured calendar, or a historical legacy reservation was confirmed. 'booking_pending': the provider outcome is unresolved; do not create another booking or seek owner approval — repeat confirm_booking later to read the stored outcome. 'pending_merchant': a historical merchant-review reservation awaits a business decision — see message. 'already_confirmed': this reservation was confirmed earlier (safe replay)."

Changed1 schema field changedSep 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "message": {
+      "description": "Present with pending_merchant: customer-facing text to relay",
+      "type": "string"
+    },
+    "reservation_id": {
+      "format": "uuid",
+      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+      "type": "string"
+    },
+    "status": {
+      "description": "'confirmed': the code was right and the slot is now exclusively held. 'pending_merchant': the code was right; the business must accept within 24 hours and may decline — see message. 'already_confirmed': this reservation was confirmed earlier (safe replay).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "reservation_id"
+  ],
+  "type": "object"
+}

AddedAug 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already signal a non-read, destructive operation, but the description adds valuable behavioral context beyond them: a verified code attempts a direct calendar commit with no owner approval, booking_pending means the provider outcome is uncertain with no automatic provider retry, and paid bookings have no code. This meaningfully explains side effects and state transitions beyond the structured hints.

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?

The description is dense but every sentence earns its place: it states the core action first, then covers the code rule, commit behavior, pending outcome, and the paid-booking exception. There is no filler or repetition of schema details.

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?

For a mutating, stateful confirmation tool, the description covers the main success path, the uncertain provider outcome, the no-retry behavior, and the paid-booking branch. An output schema exists, so return-value details do not need to be in the description, and schema validation covers the code format. Nothing essential for selecting and invoking this tool correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds extra value by explaining the lifecycle of the code parameter: it must be customer-supplied, never generated or fetched, and is absent for paid bookings. This goes beyond the schema's own documentation, though slug and reservation_id semantics remain mostly schema-dependent.

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?

The description states a specific verb and resource ('Confirm a reservation made with reserve_slot') and clearly distinguishes this from related payment and booking tools. It also names the alternative for paid bookings, so an agent can tell it apart from create_booking_payment_link and reserve_slot without opening their schemas.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance and exclusions: use it when a reservation exists and a customer supplies the code; for paid bookings with payment.required=true, route to create_booking_payment_link; for payment_in_flight, wait; for booking_pending, repeat confirm_booking later. These conditions and alternatives are stated directly rather than left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AdvocateMCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.