Skip to main content
Glama

Request a booking

request_booking

Book a time for your user (confirm the details with them first). It goes to Ryan as a request: nothing is charged, he texts to confirm, and the customer gets an email with the details and a private link to change or cancel.

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": {
      "service": "<service>",
      "vehicle": "<vehicle>",
      "start_time": "<start_time>",
      "street": "<street>",
      "city": "<city>",
      "zip": "<zip>",
      "name": "<name>",
      "phone": "<phone>",
      "email": "<email>"
    },
    "name": "request_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes
cityYes
nameYes
unitNo
emailYesWhere the confirmation and change-or-cancel link go.
notesNo
phoneYesMobile number; Ryan texts to confirm.
streetYesStreet address where the car will be.
add_onsNoOptional extras: pet-hair = Pet hair removal (+$35; with interior/full); shampoo = Carpet & seat shampoo (+$60; with interior/full); odor = Odor elimination (+$50; with interior/full); headlights = Headlight restoration (+$60; with wash/interior/exterior/full); engine = Engine bay cleaning (+$45; with exterior/full).
serviceYesService: wash = Maintenance wash (from $79); interior = Interior detail (from $169); exterior = Exterior detail (from $149); full = Full detail (from $249); ceramic = Ceramic coating (from $899, one-time only).
vehicleYesVehicle size: sedan = Sedan / coupe; suv = SUV / crossover; truck = Truck; xl = 3-row / van / XL.
conditionNoHow it looks right now (first visit only; default lived): fresh = Basically clean; lived = Lived-in; kids = Kid-tested (+15%); dog = The dog's car now (+30%); yikes = We don't judge (+50%).
how_oftenNoonetime (default), biweekly = every 2 weeks (15% off each visit), monthly = every 4 weeks (10% off).
ok_to_textNoBooking updates by text (default true).
start_timeYesA start_time exactly as find_open_times returned it (ISO 8601, UTC).
mud_run_codeNoA Mud Run code (MUD-XXXX) earned with this email: 10% off a first Full detail.
vehicle_descriptionNoe.g. "white 2021 Tesla Model 3".
gate_or_parking_notesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds substantial context beyond them: nothing is charged, the booking goes to Ryan as a pending request, he texts to confirm, and the customer receives an email with a private change/cancel link. Gaps remain around non-idempotency (no warning against duplicate submissions) and what the call returns.

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?

Two sentences, front-loaded with the action and its prerequisite, then the outcome the agent needs to relay to the user. Every clause carries information — no filler.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 18-parameter, 9-required mutation with no output schema, the description should say what comes back (a booking id? a pending-status confirmation?) and warn that repeated calls create separate requests. It covers the customer-facing outcome well but leaves the agent's own operational questions unanswered.

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?

The schema description coverage is 67% and carries the enums, pricing, and add-on compatibility rules itself. The description adds no parameter-level meaning beyond a general 'confirm the details' nudge, so the baseline 3 is appropriate for a schema doing most of the work.

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 time for your user') and immediately clarifies that the output is a request rather than a confirmed appointment. This distinguishes it from siblings like get_booking or find_open_times, though no sibling is named explicitly.

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?

The parenthetical '(confirm the details with them first)' is a genuine workflow prerequisite, which is more than most definitions offer. However, it never states that start_time must come from find_open_times, that check_service_area should be verified first, or that apply_mud_run_code is a separate call — the agent must infer the sequencing from sibling names.

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