Skip to main content
Glama

See times to visit

visit_times
Read-only

Checks a visit time the buyer stated in chat, or lists up to three times the dealership is open. It sends nothing, and it never picks a time: the buyer picks. The buyer must have gone ahead with this car before the time can be sent.

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>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "visit_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
slotNoThe visit time the buyer stated. Leave it out to list the times the dealership is open.
rowKeyYes
offerVersionYesThe offer's version, from requests_get.
idempotencyKeyYesA key you made up for this request: 1 to 255 printable characters. book_visit sends with the same key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, but the description still adds real value: 'It sends nothing' confirms zero side effects, and 'it never picks a time: the buyer picks' rules out the most likely agent misbehavior. The precondition about the buyer having gone ahead with this car is useful gating context, though the phrase 'before the time can be sent' is slightly ambiguous about which operation it gates.

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 short sentences with the primary function front-loaded and the safety caveats immediately after, so an agent can stop reading early and still call correctly. The final precondition sentence is the weakest link, since 'the time can be sent' is vague, but nothing is padded.

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?

With five parameters, a nested object, and no output schema, the description should describe what comes back, and it only partly does via 'lists up to three times.' It never explains the identifier parameters (id, rowKey) or the failure mode when the stated time isn't available, which matters for a check-style 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 coverage is 60% and the schema itself already explains slot's optionality, the instant format, offerVersion's source, and the idempotencyKey's purpose. The description adds little parameter-level meaning beyond noting the list cap of three; it says nothing about id, rowKey, or how offerVersion interacts with verification.

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 names a specific verb and resource: checking a buyer-stated visit time, or listing up to three open dealership times. It also explicitly separates itself from the write path by saying it 'sends nothing' and 'never picks a time: the buyer picks,' which lets an agent distinguish it from book_visit 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 Guidelines4/5

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

It states the two triggering conditions clearly: the buyer stated a time in chat, or the agent needs to surface available times. It also gives a precondition ('The buyer must have gone ahead with this car before the time can be sent'). It stops short of naming book_visit as the explicit next step, so the hand-off is implied rather than stated.

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