Skip to main content
Glama

Pick a time to visit

book_visit
Destructive

Sends the visit time the buyer confirmed. The dealership gets the buyer's name, phone number and email. It needs the previewToken that visit_times returned, and the same idempotencyKey as that visit_times call. Before the buyer has gone ahead with this car, it answers go_ahead_first.

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": {
      "id": "<id>",
      "rowKey": "<rowKey>",
      "offerVersion": "<offerVersion>",
      "slot": "<slot>",
      "previewToken": "<previewToken>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "book_visit"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
slotYesThe time from the visit_times answer the buyer confirmed.
rowKeyYes
offerVersionYesThe offer's version, from requests_get.
previewTokenYesThe previewToken from visit_times for the same time.
idempotencyKeyYesThe same key as the visit_times call: 1 to 255 printable characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this a non-read-only, open-world, destructive write, and the description adds valuable context by naming the real side effect: the dealership receives the buyer's name, phone and email. However, it says nothing about failure modes, whether a re-send duplicates the visit, or what happens if the previewToken has expired, so the additional disclosure is partial.

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 its side effect, with no filler. The clause "it answers go_ahead_first" is slightly opaque in phrasing, but overall the delivery is efficient rather than verbose.

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 a six-required-parameter mutation with no output schema, the description covers the precondition, the PII side effect, and the token/key dependencies, which is a reasonable amount. It still leaves the identity parameters unexplained and gives no sense of the response or error surface, so an agent could call it but not fully predict the outcome.

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 coverage is 67%, and the description mostly restates what the schema already says about previewToken and idempotencyKey, which are already documented at the property level. It adds nothing about id and rowKey, the two bare string parameters with no schema descriptions, so it does not compensate for the remaining coverage gap.

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?

The description gives a concrete verb and resource ("Sends the visit time the buyer confirmed") and implicitly positions itself downstream of visit_times by requiring that call's previewToken. It is clear what the tool does, though the phrasing is a bit indirect compared to a direct statement like "books the appointment."

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?

It supplies an explicit precondition and a fallback: if the buyer has not gone ahead with the car, the answer is go_ahead_first. It also states the tool must follow visit_times by reusing the previewToken and idempotencyKey. There is no explicit when-not guidance beyond the go_ahead_first gate, so it falls short of a 5.

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