Skip to main content
Glama

Mechanic Atlas Auto Manual

Mechanic Market Numbers

mechanic_market
Read-onlyIdempotent

Auto repair business counts by trade, shops per 100,000 people and mechanic pay for a US state, or a county in it. From the Census Bureau and the Bureau of Labor Statistics.

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": {
      "state": "<state>"
    },
    "name": "mechanic_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesState name or two letter code
countyNoOptional county name

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety behavior is fully covered structurally. The description adds genuine value by disclosing data provenance (Census Bureau, Bureau of Labor Statistics), which signals official/statistical rather than live operational data. It stops short of describing return shape, units of pay (annual vs hourly), or how missing county data is handled.

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 sentences with no filler; the metric list is front-loaded and the provenance trails as a useful qualifier. The phrasing 'for a US state, or a county in it' is slightly awkward but conveys the hierarchy efficiently. Nothing extraneous, though nothing is especially well structured either.

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 read-only statistics lookup with no output schema, the description covers the essentials: what metrics, at what granularity, from which sources. The main residual gap is the shape and units of the return payload, which matters slightly more here because no output schema exists. Given the tool's low complexity, it is otherwise sufficient 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 coverage is 100%, with both parameters described in the schema itself, so the baseline is 3. The description adds a little: it clarifies that the state must be US and that the county is subordinate to that state ('a county in it'), which reinforces the containment relationship. It adds no format guidance beyond what the schema's 'name or two letter code' already says.

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?

Names a specific resource (auto repair business statistics) and enumerates the metrics returned: business counts by trade, shops per 100,000 people, and mechanic pay. The retrieval verb is only implied ('counts', 'pay'), but an agent can tell what data comes back. No sibling differentiation, though the sibling list (recalls, repair_guides, complaints) contains no comparable statistics tool, so the omission costs little.

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 through the geographic scope: query a US state, optionally narrowed to a county. There is no explicit statement of when to reach for this tool versus e.g. repair_jobs, and no note on prerequisites, coverage limits, or what to do when county data is unavailable. Adequate for a simple lookup, but guidance is inferred 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