Skip to main content
Glama

Confirm this car

commit_confirm
Destructive

The card's Confirm button calls this tool. The assistant does not call it.

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

Input Schema

NameRequiredDescriptionDefault
modeNoHow the buyer will finish.
slotNoThe time the buyer picked, or null.
wordsIdNoThe id of the words the buyer saw.
dealSetIdYesThe id of the request.
wordsSha256NoThe hash of the words the buyer saw.
confirmTokenNoThe token the card holds.
shareContactNoWhether the buyer shares contact details.
negotiationIdYesThe id of the offer.
idempotencyKeyNoThe key the card holds.
expectedOfferVersionNoThe version of the offer the buyer saw.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the agent knows this is an irreversible, world-affecting write. The description adds only the fact that a UI card invokes it, and says nothing about what is destroyed or committed, whether contact details are shared, or whether the card's confirmToken/idempotencyKey guard against duplicate confirmations.

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?

Two short sentences with no filler, and the most decision-relevant statement ('The assistant does not call it') is placed where it will be read. Nothing is wasted, though the brevity reflects under-specification rather than disciplined precision.

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

Completeness2/5

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

This is a destructive, open-world write with ten parameters and no output schema, yet the description explains none of its effects, preconditions, or failure modes. For a confirmation tool that finalizes a deal, the absence of any statement about irreversibility or side effects is a substantial gap.

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 all ten parameters (mode, slot, confirmToken, expectedOfferVersion, idempotencyKey, etc.) are already documented in the schema. The description adds no additional meaning, such as how expectedOfferVersion or confirmToken should be sourced, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the invocation path (the card's Confirm button) but never states the actual effect of the tool — what a 'confirm' commits, what state changes, or what deal outcome results. The title 'Confirm this car' is essentially restated rather than explained, leaving an agent unable to say what this tool does beyond its name.

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 unambiguous exclusion: 'The assistant does not call it.' For an agent, that is a decisive routing rule and effectively prevents misuse. It stops short of a 5 because no positive context or named alternative path (e.g., which sibling the assistant should use instead of the card) is provided.

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