Skip to main content
Glama

Sirfus CAR

Get a planning estimate from local prices

car_get_estimate
Read-onlyIdempotent

A price range for the job researched from local prices (with where the prices came from), not a quote. Contacts no one. Returns an estimateId; an estimateId passed with car_send_request gives the business the same scope and range. No sign-in needed.

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": {
      "service": "<service>"
    },
    "name": "car_get_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNo5-digit US ZIP code (or give where)
whereNo"City, ST" when there is no ZIP
answersNoQuestion id -> option value (a list for multi-choice questions)
serviceYeshouse-cleaning, bathroom-remodel, handyman, plumbing-repair or hvac (car_estimate_services lists them with their questions)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavior beyond those fields: it contacts no one, requires no sign-in, returns price provenance, and clarifies that the result is an estimate rather than a quote. It does not cover estimate expiration or rate limits, but it substantially enriches the behavioral picture.

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?

The description is short, front-loaded, and every sentence contributes useful information. It leads with the core result, then adds side-effect, return-value, and authentication context without unnecessary wording. The parenthetical source note is compact and relevant.

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 does the important work of explaining that the tool returns a price range with source information and an estimateId. It also covers the no-contact and no-sign-in constraints, which matter for an open-world read-only tool. The nested answers object is only indirectly covered via the service schema reference, but the overall definition is complete enough to call correctly.

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 the input schema already documents zip, where, answers, and service in detail. The description mentions the returned estimateId and its later use with car_send_request, but it adds little meaning about the input parameters themselves beyond what the schema provides. This matches the baseline of 3 when the schema does the heavy lifting.

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

Purpose5/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: it returns a price range for a job researched from local prices, explicitly not a quote. It also distinguishes itself from car_send_request by explaining that the returned estimateId preserves the same scope and range when passed to that sibling. An agent can tell exactly what this tool produces without opening another schema.

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?

The description gives clear usage context: use it for a planning estimate that contacts no one and needs no sign-in, and later pass its estimateId to car_send_request. It names the relevant sibling and the handoff relationship, but it does not spell out explicit when-not conditions or a full comparison against every alternative. The guidance is strong but slightly implicit rather than fully instructive.

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