Skip to main content
Glama

Mechanic Atlas Auto Manual

Find Vehicle

find_vehicle
Read-onlyIdempotent

Look up a vehicle by make and model, with an optional year. Returns the engines, transmissions and drive types built that year, how many repair jobs apply, and the free factory manual archive links.

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": {
      "make": "<make>",
      "model": "<model>"
    },
    "name": "find_vehicle"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeYesMake, for example Toyota
yearNoModel year, for example 2015
modelYesModel, for example Camry

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's added value is the return payload — engines, transmissions, drive types, repair job counts and 'free factory manual archive links' — which is useful context, though it says nothing about coverage limits (e.g. what happens when the year is omitted) or failure modes.

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?

Two sentences, zero waste. The lookup key is front-loaded and the return contents follow immediately, matching the order an agent needs them.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 carries the burden of explaining returns and it does so specifically, which is a real strength. However, for a 3-parameter lookup with an optional filter, it leaves two operator-relevant gaps: the behavior when year is omitted (all years?) and the behavior when make/model matches nothing or matches multiple vehicles.

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?

Schema coverage is 100% with examples for all three parameters, so the baseline is 3. The description earns above baseline because it clarifies that the optional year scopes the returned engines/transmissions/drive types to that model year, which is meaning the schema does not convey; it does not, however, say what an omitted year returns.

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?

A specific verb and resource: 'Look up a vehicle by make and model, with an optional year.' It also names the lookup key, which tells an agent this is the base vehicle-resolution tool rather than a downstream one like complaints or repair_jobs. It stops short of explicitly declaring how it differs from any named sibling, so it sits just below 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 implied by the description rather than stated: an agent can infer this is the entry point that resolves a vehicle before calling sibling tools. There is no explicit when-to-use, when-not-to-use, or named alternative, and no statement about what to do when make/model is ambiguous or unknown.

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