Skip to main content
Glama
Sign In

JDM Factory Service Manuals

by io.github.balexandrov
OverviewDiscussionsAdmin

Table of contents

get_contents
Read-onlyIdempotent

List the files (sections) of a manual with what each covers, page counts and links. With 'file' (its full path, or its name within 'manual'), list that file's bookmarks (its own table of contents) instead.

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

Input Schema

NameRequiredDescriptionDefault
fileNo
manualYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond them by disclosing the return content ('what each covers, page counts and links') despite there being no output schema, which is exactly the kind of behavioral detail the agent needs. It does not cover pagination or limits.

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?

Two sentences, front-loaded with the default behavior and then the parameter-driven variant. No filler wording; the parenthetical clarifications are load-bearing rather than decorative.

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-parameter, read-only tool with no output schema, the description covers both modes, parameter interpretation, and the shape of returned data. Only minor gaps remain, such as whether 'file' matching is strict or fuzzy and any limits on listing size.

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 description coverage is 0%, so the description must carry the parameter meaning, and it does: 'file' is described as either a full path or a name within 'manual', and the flip in behavior when it is present is stated. 'manual' itself is only implicitly defined, which keeps this from a 5.

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?

Opens with a specific verb+resource: 'List the files (sections) of a manual', and adds what the listing contains (coverage, page counts, links). It also describes the alternate mode (listing a single file's bookmarks), so an agent can picture both behaviors. It does not explicitly contrast itself with siblings like read_pages or search.

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?

The second sentence gives a clear conditional: when 'file' is supplied, the tool returns that file's own bookmarks instead of the manual-level listing. That is real when-to-use guidance tied to a parameter, though there are no explicit exclusions or pointers to alternative tools for other needs.

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 toolsInspect
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.

Resources