Skip to main content
Glama

Mechanic Atlas Auto Manual

Factory Manual Links

factory_manual_links
Read-onlyIdempotent

Links to the free factory service manual archives (Operation CHARM and LEMON Manuals) for a year and make, and whether each archive has that year.

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

Input Schema

NameRequiredDescriptionDefault
makeYesMake, for example Toyota
yearYesModel year, for example 2015

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/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. The description adds genuinely new behavioral context by disclosing the return payload: a link per archive plus a per-archive indication of whether that year is covered, which matters because there is no output schema. It does not say what a missing year yields (null link vs omitted), keeping it below 5.

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?

One sentence, front-loaded with the resource and the archives named, with no filler. The trailing clause 'and whether each archive has that year' is slightly awkward but does carry real information about the return value, so it earns its place.

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?

For a two-parameter read-only lookup this is close to adequate, and the description does explain what comes back. It omits how unavailable years are represented in the response and any coverage limits, which an agent would need to interpret results correctly given there is no output schema.

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 both parameters (make, year) are already documented with examples in the schema. The description adds only a restatement that both are required inputs and no format, range, or validity constraints (e.g., supported year span, US-market assumption), so the baseline 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 states a concrete resource (links to the free factory service manual archives Operation CHARM and LEMON Manuals) and the keying inputs (year and make), which is specific enough to separate it from siblings such as repair_guides and full_manual. It stops short of naming an alternative explicitly, so it sits at a clear 4 rather than 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 only implied: an agent can infer this is the tool for obtaining free factory manual links, but the description never says when to prefer it over full_manual or repair_guides, nor any prerequisite or exclusion. That is the definition of implied rather than explicit guidance.

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