Skip to main content
Glama

Sirfus CAR

Record the person's pick from an outside search

car_pick_outside

Records the business the person chose. CAR does not contact it or share the person's details; the person contacts it directly. Returns a request (status outside_picked) for status and webhooks.

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": {
      "searchId": "<searchId>",
      "optionId": "<optionId>"
    },
    "name": "car_pick_outside"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionIdYesThe option the person picked: "1", "2" or "3"
searchIdYesThe searchId car_find_outside returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses the important side-effect boundary: CAR does not contact the business or share the person's details, and the person follows up directly. It also reports the resulting status (outside_picked) and that the request feeds status and webhooks. It omits duplicate-call behavior, which matters given idempotentHint=false.

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?

Three short, front-loaded sentences with no filler; the recording action comes first and consequences follow. The final sentence ('Returns a request (status outside_picked) for status and webhooks') is slightly compressed and reads awkwardly.

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 two-parameter write tool with annotations and no output schema, the description covers the action, the non-contact guarantee, and the returned status. It lacks only the explicit link to the preceding search call and any note on repeated picks.

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% and both parameters are documented there, including the allowed optionId values. The description adds nothing about searchId or optionId semantics, 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?

The description states a specific verb and resource — 'Records the business the person chose' — which clearly separates it from the discovery tool car_find_outside. It does not explicitly name a sibling it differs from, keeping it just short of a 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 phrase 'the business the person chose' and the title's 'outside search' suggest this follows an outside search, but the description never states the prerequisite explicitly (the searchId dependency lives only in the schema) or when not to use it versus car_confirm_person or car_send_request.

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