Skip to main content
Glama

Sirfus CAR

Services the planning estimate covers

car_estimate_services
Read-onlyIdempotent

Lists the services the planning estimate covers (house cleaning, bathroom remodel, handyman, plumbing repair, HVAC) with each one's questions and option values, and which CAR categories map to them. No sign-in needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "car_estimate_services"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the bar is lower. The description still adds real value the annotations don't: it discloses the auth situation ('No sign-in needed') and, with no output schema, effectively describes the payload contents (questions, option values, CAR category mapping).

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?

A single front-loaded sentence with the parenthetical examples doing useful work rather than padding. No redundant restatement of the title and no wasted clauses.

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 zero-parameter, read-only reference tool with no output schema, the description is nearly sufficient: it names the item types returned and the category mapping, which is what an agent needs to decide whether to call it. It could go further by stating how this list relates to the estimate-creation flow, but the essential information is present.

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

Parameters4/5

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

There are zero parameters, so the baseline is 4 and there is nothing the description could clarify beyond that. No parameter-level meaning is missing.

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 ('Lists') and a specific resource ('the services the planning estimate covers'), then enumerates the concrete service names (house cleaning, bathroom remodel, handyman, plumbing repair, HVAC) so an agent knows exactly what comes back. It stops short of naming a sibling tool, so differentiation from car_get_estimate is inferred from the resource rather than asserted.

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?

'No sign-in needed' gives a useful prerequisite but is not when-to-use guidance; nothing says to call this before requesting or configuring an estimate, nor when to skip it in favor of car_get_estimate. Usage is implied by the reference-data nature of the tool rather than stated.

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