Skip to main content
Glama

Mechanic Atlas Auto Manual

Full Manual For One Car

full_manual
Idempotent

The full manual for one year, make and model: sourced capacities, fluids, torques and intervals for each engine, and the step by step procedure for any job (tools, specs to check, steps, what to do after, cautions). The first pull of a car unlocks it for 30 days and uses a free pull, a membership car or $1 from the wallet. Pulls on an unlocked car are free.

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

Input Schema

NameRequiredDescriptionDefault
jobNoOptional job, for example front brakes, timing belt or spark plugs. Leave out for the spec sheet and the job list
keyYesThe person's access key from get_access
makeYesMake, for example Toyota
yearYesModel year, for example 2015
modelYesModel, for example Camry
engineNoOptional engine, for example 2.5L or 5.3L V8
confirmNotrue only after the person says yes to a $1 charge

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only mark this as non-read-only and idempotent; the description adds the economically critical facts an agent cannot get elsewhere: first pull consumes a free pull, a membership car, or $1 from the wallet, and the car then stays unlocked for 30 days with free repeat pulls. That is real behavioral disclosure beyond structured fields. It does not describe failure modes, such as insufficient wallet balance or an unmatched year/make/model.

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?

Three sentences, no filler, and the most decision-relevant content (what the manual contains) is front-loaded before the cost rules. Slight deduction for the awkward phrase 'a membership car', which reads as a typo for 'membership card' and briefly muddies the billing sentence.

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 7-parameter retrieval tool with no output schema, the description covers the return content, the optional-job behavior, and the cost/unlock model, which is what an agent needs before committing a paid call. The gaps are error behavior and vehicle-not-found handling, which matter less than getting the charge semantics right.

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%, so a baseline of 3 applies; the description nudges above it by tying the charge to confirmation ('after the person says yes to a $1 charge') and by clarifying that the job parameter is what selects procedure output versus the plain spec sheet. The remaining parameters (key, year, make, model, engine) are already fully documented in the schema.

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 names the resource precisely ('the full manual for one year, make and model') and enumerates its payload: capacities, fluids, torques, intervals per engine, plus step-by-step job procedures. That is far more specific than the bare name. It stops short of explicitly contrasting itself with lookalike siblings such as repair_guides or factory_manual_links, leaving that distinction to inference.

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?

Useful context is implied: omit 'job' to get the spec sheet and job list, supply it for a procedure. The pricing and 30-day unlock rules also tell the agent when a call is cheap versus billable. However, there is no explicit statement of when to prefer this over repair_guides or factory_manual_links, and no guidance on what to do if the vehicle is not found.

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