Skip to main content
Glama

Show the confirm card

show_go_ahead_card
Read-only

Shows the card where the buyer can go ahead with one car on a request. It is for a buyer who said they want to go ahead with this car. An offer can be read without this card through requests_get. It takes the request's dealSetId (id in requests_list) and the car's negotiationId (rowKey in requests_get). It does not go ahead for the buyer. Only the buyer does, by tapping Confirm in the card. It answers one state: ok (the card shows the offer), choose_on_request_page (the buyer goes ahead with this car on their request page), no_offer_yet (the dealership has not sent an offer, so there is nothing to go ahead with), not_in_card (the card cannot offer this car, and the buyer sees where it stands on their request page), not_found or unavailable. An entry of kind single answers choose_on_request_page, or not_in_card when it has ended.

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": "show_go_ahead_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
surfaceNoWhich card sent this: `offer_card` is the offer card.
dealSetIdYesThe id of the request, from `id` in requests_list.
negotiationIdYesThe car the buyer named, from `rowKey` in requests_get.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the readOnly/destructive annotations by stating that the tool itself does not commit anything — only the buyer, by tapping Confirm — which prevents an agent from mistaking this for a write. It also discloses the range of outcomes (including the no-offer, not-in-card and ended cases) that a caller must handle. Missing only ordering/rate or idempotency behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the middle repeats schema-derived id/rowKey mappings, and the outcome list is delivered as one long run-on sentence. The closing line about an entry of kind `single` introduces unexplained jargon that no schema field anchors, costing the reader more than it gives.

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 appropriately carries the return-state enumeration so an agent can branch on ok/choose_on_request_page/no_offer_yet/not_in_card/not_found/unavailable. The only gap is the opaque `single`-kind sentence, which alludes to a concept the definition never defines.

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%, so both required parameters and the surface enum are already documented in the schema, including their source fields (id in requests_list, rowKey in requests_get). The description repeats that same mapping rather than adding new meaning, so the baseline of 3 applies.

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

Purpose4/5

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

States a concrete verb and resource: it shows a confirmation card for one car on a request, and clarifies that reading an offer alone does not require it. The word "card" is a domain/UI metaphor an agent must already know, but the effect of the call is clear and distinct from requests_get.

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?

Explicitly scopes the call to a buyer who has said they want to go ahead with this car, and names an alternative (requests_get) for simply reading the offer. It does not enumerate when-not to call it or what to do when the card is unavailable, so it falls short of full routing guidance.

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