Skip to main content
Glama

Cancel the visit

cancel_visit
Destructive

Cancels the buyer's visit to this dealership. Use it only when the buyer says to. The buyer's go-ahead on this car stays. withdraw is different: it ends the go-ahead, and the visit with it. If the dealership already had the visit, it is told the visit is off (told: true). With told: false, the dealership never had the visit, so it is not told. The first change from an assistant that is not ChatGPT or Claude may need the buyer to tap a confirm link Ridekick emails.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the request, from requests_list. For an entry of kind `single`, this is the entry's `id` from requests_list.
rowKeyYesThe row key of the one dealership, from requests_get. An entry of kind `single` in requests_list has no rows: its rowKey is that entry's `id`, the same value as `id`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, yet the description still adds substantive behavior: the buyer's go-ahead survives the cancellation, and the dealership is or is not notified depending on whether it had already taken the visit ("told: true" vs "told: false"). It also surfaces an auth dependency — a Ridekick email confirm link on the first change from a non-ChatGPT/Claude assistant — which no structured field conveys.

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?

Front-loads purpose, then the sibling distinction, then behavioral outcomes, then the auth caveat — a sensible ordering with no filler. It is slightly dense and reads as a run of short declaratives, but each sentence carries distinct information.

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

Completeness5/5

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

For a destructive, open-world mutation with no output schema, the description covers what is destroyed, what is preserved, what the caller may learn back (the `told` flag), and a possible confirmation step. Nothing an agent needs in order to call this safely is missing.

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 100%, and both parameters are documented there in detail, including the rowKey-id equivalence for `single` entries. The description adds no further meaning about `id` or `rowKey`; the `told` token it references is a result signal, not an input. Baseline 3 is correct when the schema carries the full parameter burden.

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 ("Cancels the buyer's visit to this dealership") and immediately distinguishes itself from the closest sibling by naming it: "withdraw is different: it ends the go-ahead, and the visit with it." An agent can pick between cancel_visit and withdraw without opening either 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 gating condition — "Use it only when the buyer says to" — which is a when-to-use rule, not a hint. It also names the alternative (withdraw) and the condition that selects it, so both the positive case and the exclusion are covered.

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