Skip to main content
Glama

Withdraw the go-ahead on this car

withdraw
Destructive

Ends the buyer's go-ahead on this car, and the visit with it if there is one. Use it only when the buyer says to. cancel_visit is different: it ends only the visit and keeps the go-ahead. Going ahead with another car is a separate step. If the dealership already had the go-ahead, it is told the buyer is not going ahead (told: true). With told: false, the dealership never had it, 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": "withdraw"
  }
}

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.5/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/readOnlyHint annotations: it discloses the collateral effect (the visit is ended too), the dealership notification semantics (told: true vs. told: false), and an authentication dependency (a confirm link emailed for the first change from a non-ChatGPT/Claude assistant). These are exactly the side effects an agent needs before invoking a destructive tool.

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-loaded with the action, then the constraint, then the alternative, then side effects — a sensible ordering with no filler. Some sentences are telegraphic to the point of needing a re-read, which costs a little clarity.

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?

With no output schema, the description correctly takes on the return semantics via told: true/false, and the auth caveat covers the main failure mode. It stops short of stating what happens on an already-withdrawn go-ahead or a bad rowKey, which leaves a gap for a destructive operation.

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 description coverage is 100%, so both id and rowKey are fully documented in the schema, and the description adds no format or derivation detail beyond it. The description's added meaning is behavioral rather than parameter-level, so the baseline 3 applies.

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: "Ends the buyer's go-ahead on this car, and the visit with it if there is one." It immediately distinguishes itself from the sibling cancel_visit, so an agent can tell the two apart 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 precondition ("Use it only when the buyer says to") and names the alternative plus the condition that selects it ("cancel_visit is different: it ends only the visit and keeps the go-ahead"). It also rules out an adjacent intent ("Going ahead with another car is a separate step"), which prevents a common mis-selection.

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