Skip to main content
Glama

plateau-candy

book_consultation

Book a consultation with Plateau Candy. Requires a specific time slot from get_availability. Notes required (min 10 chars). Booking requires manual confirmation.

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": {
      "event_type_id": "<event_type_id>",
      "start_time": "<start_time>",
      "name": "<name>",
      "email": "<email>",
      "notes": "<notes>"
    },
    "name": "book_consultation"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull name
emailYesEmail for confirmation
notesYesTopic/reason for consultation (min 10 chars)
start_timeYesISO 8601 start time (from get_availability)
event_type_idYesEvent type ID

Output Schema

NameRequiredDescriptionDefault
submittedYes
booking_idNo
booking_urlYes
requires_confirmationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the write/external nature is covered. The description adds genuinely new behavior: 'Booking requires manual confirmation,' which tells the agent the booking is not immediately final and no instant confirmation should be assumed. It does not describe failure modes or duplicate-booking behavior, keeping it from a 5.

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?

Four short sentences, front-loaded with the action and followed by the prerequisite, the constraint, and the confirmation caveat. The notes minimum-length clause duplicates the schema, which is a small redundancy but the text is otherwise tight.

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, return values need not be explained, and the description covers the action, prerequisite, key constraint, and the manual-confirmation caveat. Remaining gaps (cost, confirmation email, duplicate handling) are minor for a 5-parameter booking tool.

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 every parameter is already documented, including the notes minimum length and the get_availability provenance of start_time. The description largely restates those facts ('Notes required (min 10 chars)') rather than adding new meaning, so the baseline 3 applies.

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?

States a specific verb and resource ('Book a consultation with Plateau Candy') and names the prerequisite source of the time slot. It is distinguishable from the read-only siblings (get_availability, get_services, get_profile) by being the only booking action, though it does not explicitly contrast itself with them.

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?

Explicitly states the precondition that a time slot must come from get_availability, which is the key routing rule for this tool. It does not state when not to use it (e.g., rescheduling or cancelling an existing booking), so it falls short of full when/when-not guidance.

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