Skip to main content
Glama

Check the dealership got it

commit_handoff
Read-only

The Commit card calls this tool to read where the dealership hand-off stands after the buyer confirms a choice. The assistant does not call it. It answers one state: held (the hand-off is waiting and has not gone yet), sending (it is on its way), sent (the dealership has been told), checking (Ridekick is checking whether it went), needs_us (it has not gone through yet, and a person at Ridekick is on it), unreadable (Ridekick cannot read it right now and is checking), practice (this is a practice request, so nothing was sent to any dealership), or none (no choice has been confirmed). For checking and unreadable, it is not known whether the dealership has been told.

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": {
      "negotiationId": "<negotiationId>"
    },
    "name": "commit_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
negotiationIdYesThe id of the offer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already establish readOnly/non-destructive/closed-world, and the description goes well beyond them by documenting the full state machine, what each state means operationally (held vs sent vs needs_us vs practice), and the important caveat that for `checking` and `unreadable` it is genuinely unknown whether the dealership has been told. That unknown-state disclosure is the kind of nuance structured fields cannot carry.

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?

The critical routing fact — that the assistant does not call this — is front-loaded ahead of the state list, which is dense but earns its length because each state changes interpretation of the result. The eight-state enumeration is compressed into one paragraph with parenthetical glosses rather than a bulleted list, which costs a little scannability but wastes no words.

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 a single-parameter read tool with no output schema, the description effectively serves as the return-value contract by defining every possible `state` value and flagging which ones are inconclusive. The only gap is operational: it does not say whether an agent should poll, and how often, when it observes `checking` or `unreadable`.

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% and there is only one parameter, so `negotiationId` is already fully documented as "the id of the offer." The description adds only indirect context by framing the result as tied to a confirmed buyer choice; it never restates or extends the id's meaning. Baseline 3 is appropriate.

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 — reading the current state of the dealership hand-off after the buyer confirms a choice — and immediately distinguishes itself from the rest of the commit_* family by stating that the Commit card, not the assistant, invokes it. The enumerated state vocabulary further pins down what the tool returns, so an agent can tell it apart from commit_confirm or requests_get without opening any 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 gives an explicit caller (the Commit card), an explicit trigger (after the buyer confirms a choice), and an explicit exclusion ("The assistant does not call it"). What it does not do is name what an assistant should call instead when it needs hand-off status, so it stops short of full alternative routing.

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