JDM Factory Service Manuals

Look up a trouble code

lookup_dtc

Read-onlyIdempotent

Look up a diagnostic trouble code (P0340, C1105, U1000, or an old Nissan blink code like 34) in one car's manual and return where its diagnosis starts: page, title, and the parent bookmarks ('within'). A manual covering several engines or systems has one diagnosis per variant, so check 'within' (e.g. "QG18DE" vs "QR25DE") against the car. 'manual' is required: a manual from find_manuals, or its model folder to cover all years (listed newest year first).

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": {
      "code": "<code>",
      "manual": "<manual>"
    },
    "name": "lookup_dtc"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes
`limit`	No
`manual`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavior: one diagnosis per engine/system variant, model folders returning newest year first, and the shape of the returned location. Rate limits and result ordering for 'limit' are not discussed.

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?

Information is front-loaded: what it does and what it returns come first, parameter caveats after. Sentences are dense but each carries distinct content; the parenthetical examples and the quoted 'within' add clarity rather than noise, though the final sentence is somewhat run-on.

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 3-parameter read tool with annotations and an output schema, this covers nearly everything an agent needs: input formats, the required manual source, and variant disambiguation. The only real gap is the undocumented 'limit' parameter's effect on results.

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 0%, so the description must carry the load. It explains 'code' formats and fully explains 'manual' (required, sourced from find_manuals, folder-to-cover-all-years behavior), but 'limit' with its default of 40 is never mentioned, leaving one of three parameters undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('look up a diagnostic trouble code') and gives concrete code formats (P0340, C1105, U1000, legacy blink code 34). It also names the return payload — page, title, and parent bookmarks — so an agent knows exactly what comes back before opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the prerequisite that 'manual' is required and where to get it (output of find_manuals, or a model folder to span all years). It also gives the key disambiguation step: compare the 'within' variant against the car. No explicit exclusions or counter-case (e.g. when to use search instead), so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All JDM Factory Service Manuals tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.