Skip to main content
Glama

Sirfus CAR

Check a request's status

car_check_status
Read-onlyIdempotent

Status of a request: verify_person, matching, offered, accepted, answered, still_looking, or a final state. Final states include the business that accepted, when there is one.

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>"
    },
    "name": "car_check_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYesThe requestId returned by car_send_request

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds useful response semantics, noting that final states include the accepting business, but does not say whether non-final states can be re-polled or what a request looks like in each state.

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 clauses, front-loaded with the resource and immediately followed by the state vocabulary an agent needs. The phrase 'or a final state' is slightly vague before being clarified in the second sentence, but nothing is wasted.

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-only tool with no output schema, naming the possible return states covers the main informational gap. The remaining gap is that individual states such as 'answered' or 'still_looking' are listed but not explained.

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?

There is a single parameter and schema description coverage is 100%, with the schema already explaining that requestId is returned by car_send_request. The description adds no further meaning about the identifier, so the baseline 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 specific verb and resource ('Status of a request') and enumerates the concrete state values the agent can expect, which goes well beyond the title. It doesn't name or differentiate from siblings like car_set_webhook, which could also surface request updates, so it stops short of 5.

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 only implied: the schema mentions the requestId comes from car_send_request, so an agent can infer this is the polling follow-up. The description itself says nothing about when to check status versus using a webhook or when to stop polling at a final state.

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