Skip to main content
Glama

Inescapable Detail

Book a visit

book_visit
Idempotent

Books one visit, paid at the visit. Only when the person asked you to book and confirmed every field. David texts them to confirm. Pick a date and block from find_open_times; for service "package" the block is the whole day (send "Morning").

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": {
      "name": "<name>",
      "phone": "<phone>",
      "address": "<address>",
      "car": "<car>",
      "gate_or_parking": "<gate_or_parking>",
      "date": "<date>",
      "block": "<block>",
      "service": "<service>"
    },
    "name": "book_visit"
  }
}

Input Schema

NameRequiredDescriptionDefault
carYesThe car: year, make and model, like "2022 Honda CR-V".
dateYesYYYY-MM-DD, from find_open_times.
nameYesFirst and last name.
sizeNothree_row for a vehicle with three rows of seats (changes The Detail price) or a large truck (changes the Wash only price).
blockYes
phoneYesUS mobile number, 10 digits.
addressYesStreet address and city (or ZIP) in the Jacksonville area where the car is parked.
serviceYespackage = The Full Package (2-year protection); detail = The Detail; inside = Inside only; wash = Wash only.
gate_or_parkingYesWhere to park, and the gate code if there is one ("driveway" is fine).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / service / description
      Previous value: -"package = The Full Package; plus = The Full Package Plus; detail = The Detail; inside = Inside only; wash = Wash only."New value: +"package = The Full Package (2-year protection); detail = The Detail; inside = Inside only; wash = Wash only."
    • changedInput schema / properties / service / enum
      Previous value: -[
      -  "package",
      -  "plus",
      -  "detail",
      -  "inside",
      -  "wash"
      -]New value: +[
      +  "package",
      +  "detail",
      +  "inside",
      +  "wash"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / size / description
      Previous value: -"three_row only for a vehicle with three rows of seats (changes The Detail price)."New value: +"three_row for a vehicle with three rows of seats (changes The Detail price) or a large truck (changes the Wash only price)."
  3. Changed2 schema fields changed
    • changedInput schema / properties / service / description
      Previous value: -"package = The Full Package; detail = The Detail; inside = Inside only; wash = Wash only."New value: +"package = The Full Package; plus = The Full Package Plus; detail = The Detail; inside = Inside only; wash = Wash only."
    • changedInput schema / properties / service / enum
      Previous value: -[
      -  "package",
      -  "detail",
      -  "inside",
      -  "wash"
      -]New value: +[
      +  "package",
      +  "plus",
      +  "detail",
      +  "inside",
      +  "wash"
      +]
  4. Changed4 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"Street address and city in the Jacksonville area where the car is parked."New value: +"Street address and city (or ZIP) in the Jacksonville area where the car is parked."
    • addedInput schema / properties / car
      Added value: +{
      +  "description": "The car: year, make and model, like \"2022 Honda CR-V\".",
      +  "type": "string"
      +}
    • changedInput schema / properties / gate_or_parking / description
      Previous value: -"Gate code or where to park, if any."New value: +"Where to park, and the gate code if there is one (\"driveway\" is fine)."
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "phone",
      -  "address",
      -  "date",
      -  "block",
      -  "service"
      -]New value: +[
      +  "name",
      +  "phone",
      +  "address",
      +  "car",
      +  "gate_or_parking",
      +  "date",
      +  "block",
      +  "service"
      +]
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, idempotent write, so the safety profile is covered. The description adds genuinely new behavior: payment is collected at the visit rather than at booking, and David texts the customer to confirm afterward — a post-call side effect an agent would otherwise not know. It does not address what happens if the slot is already taken or how failures surface.

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?

Three tight sentences with no filler, and the essential precondition is front-loaded before the mechanics of picking a date and handling the package case. The phrasing is telegraphic in places, but nothing unnecessary is present.

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 an 8-required-parameter booking write with no output schema, the description covers the confirmation gate, the upstream data source, and the tricky package/block interaction. Minor gaps remain around failure modes and whether the price should be quoted to the customer, but the critical call-time information is present.

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 coverage is 89%, so the baseline is 3, and the description adds a real constraint the schema does not: for service "package" the block covers the whole day and the caller should send "Morning". The `block` enum has no schema description, so this rule meaningfully fills a gap.

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 ("Books one visit") plus a scope constraint ("paid at the visit"), and ties itself to find_open_times as the source of date and block. An agent can distinguish this create operation from the read-only siblings without opening the schema.

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?

Gives an explicit precondition for invocation — "Only when the person asked you to book and confirmed every field" — which functions as both when-to-use and when-not-to-use guidance. It also names find_open_times as the prerequisite step for choosing date and block.

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