JDM Factory Service Manuals

Find manuals

find_manuals

Read-onlyIdempotent

Find the service manual for a car. Accepts how people describe it: brand, model name, year, chassis code, engine or transmission code, e.g. "2004 Sentra 1.8", "B15", "QG18DE", "Mazda 3". Returns manuals best match first, factory service manuals before owner's manuals; pass a result's 'manual' to search / lookup_dtc / get_contents. A manual is one book: 'title', 'type' (service, wiring, body, owners, features, parts, bulletins, accessory, brochure, article, aftermarket; '' if unknown), 'format' (pdf / html) and 'lang' say which; only English books are searchable. A year folder's books share the folder: pass the folder ("Japan/Subaru/Forester/2008") as 'manual' to search them all. A result with a 'file' is one book among the loose files of a model folder: read it with read_pages(file, page) or get_contents(manual, file); search and lookup_dtc on its 'manual' cover that whole folder. A 17-character VIN or a Japanese frame number ("JZX100-0012345") is read as make, chassis code and year; the results then say how under 'read_as'. An engine or transmission code finds the books that print it, also written short or without hyphens ("k24" -> K24A3, "1jzgte" -> 1JZ-GTE); 'read_as' then says what it is ("K24: Honda engine (K24A1, K24A3 ...)").

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": {
      "query": "<query>"
    },
    "name": "find_manuals"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds real behavior: ranking (best match first, factory service manuals before owner's), the English-only searchability limit, and how VINs, frame numbers and engine/transmission codes are reinterpreted via 'read_as'. It does not state result count limits or pagination behavior for the 'limit' parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and most sentences carry unique information, but the middle degrades into a dense paragraph with an awkward mid-sentence enumeration of manual 'type' values and inconsistent line breaks. It would read much better as short paragraphs or bullets per concept (query forms, result fields, sibling handoff).

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-param discovery tool with an output schema, the description covers query interpretation, ranking, result-field meaning ('manual', 'file', 'read_as'), and downstream tool routing. The only real gap is the undocumented 'limit' and any note on result-set size, which the output schema may partially cover.

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 0%, so the description must carry the load, and it does for 'query': accepted forms (brand, model, year, chassis code, engine/transmission code), worked examples, hyphen-insensitive matching ("k24" -> K24A3, "1jzgte" -> 1JZ-GTE), and VIN/frame-number parsing. The 'limit' parameter is never mentioned, leaving one of two params 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?

Opens with a specific verb+resource ('Find the service manual for a car') and immediately bounds the tool's identity against siblings by explaining that a result's 'manual' is the key to feed search / lookup_dtc / get_contents. An agent can tell this is the entry-point discovery tool, not a content reader.

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

Usage Guidelines5/5

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

Explicit routing guidance: results go to search, lookup_dtc, or get_contents; loose files go to read_pages(file, page) or get_contents(manual, file); a year folder path can be passed as 'manual' to search the whole folder. It names alternatives and the exact condition that selects each.

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.