Skip to main content
Glama

Sirfus CAR

Confirm the person with their text code

car_confirm_person
Idempotent

Sends the 6-digit code the person received. When it is right, the request goes to one checked business. Five wrong codes close the request.

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": {
      "requestId": "<requestId>",
      "code": "<code>"
    },
    "name": "car_confirm_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe 6-digit code the person received by text
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The description discloses behavior the annotations do not: a correct code routes the request to exactly one checked business, and five wrong codes close the request entirely. That lockout consequence is operationally important and is not captured by readOnlyHint=false / destructiveHint=false. Minor tension exists between 'five wrong codes close the request' and idempotentHint=true, but the accrual is a failure counter rather than a resource mutation, so it does not rise to a contradiction.

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

Conciseness5/5

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

Three short sentences with zero filler; the action and its success condition come first, and the failure consequence follows. Nothing is repeated unnecessarily.

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

Completeness3/5

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

For a two-parameter confirmation tool the core outcome is covered, but the description says nothing about requestId or what a successful call returns (confirmation status vs. business details), which matters since there is no output schema to fall back on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: code is documented in the schema, but requestId is undocumented in both schema and description. The description restates that the code is the one received by text, adding essentially nothing beyond the schema, and gives no clue about what requestId refers to or where to obtain it.

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?

A specific verb and resource: it sends the 6-digit code the person received to confirm them, and states the downstream effect (the request goes to one checked business). That is enough to separate it from request-creation siblings like car_send_request, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: you call it after a person has received a code by text. There is no explicit when-not guidance (for example, what to do if no code arrived, or whether car_check_status should be polled instead), so the agent must infer its place in the flow.

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