Skip to main content
Glama

Sirfus CAR

Check what CAR can do for a request

car_find_business
Read-onlyIdempotent

Reads a request and says which category and safety tier it falls in, and whether checked businesses that fit are signed up near the place. When the kind of business is unclear it returns needsDetail with a question and choices for the person. Contacts no one and returns no contact details. 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": {
      "what": "<what>",
      "where": "<where>"
    },
    "name": "car_find_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
whatYesWhat the person needs
whereYesCity and two-letter US state, e.g. "Tampa, FL"
categoryNoOptional. A category slug from /v1/categories that the person picked, for example after a needs_detail question. Without it, CAR reads the request.

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?

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context: no person is contacted, no contact details are returned, no sign-in is required, and an ambiguous business kind triggers a needsDetail response with a question and choices. Only the exact return shape beyond category/tier/needsDetail is left unstated, which matters somewhat since there is no output schema.

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?

Four short sentences, front-loaded with the core action and followed by the fallback branch and the safety/no-contact guarantees. Every sentence carries information, though 'checked businesses that fit' is slightly vague phrasing that could be tightened.

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 three-parameter read-only lookup with no output schema, the description covers what comes back (category, safety tier, signup availability, or a needsDetail clarification), plus the no-contact and no-auth guarantees. It does not address edge cases such as invalid or non-US locations, but nothing essential to calling it correctly is missing.

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 schema already explains 'what', 'where' (city plus two-letter US state), and 'category' including the fallback behavior when omitted. The description adds no parameter-level meaning beyond that, so the baseline of 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 gives concrete verbs and outputs: it reads a request, classifies it into a category and safety tier, and reports whether matching checked businesses are signed up near the place. That is far more specific than the name car_find_business suggests, and 'contacts no one and returns no contact details' distinguishes it from outreach siblings like car_send_request. It stops short of explicitly naming a sibling to use instead, so it is clear but not fully differentiated.

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: you call this when you have a request ('what') and a place ('where') and need to know whether CAR can serve it. The description never states when to prefer a sibling such as car_find_outside or car_check_status, nor any exclusion conditions. The needsDetail branch describes a behavior, not a when-to-use rule.

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