Skip to main content
Glama
Sign In

JDM Factory Service Manuals

by io.github.balexandrov
OverviewDiscussionsAdmin

Page image

page_image
Read-onlyIdempotent

Render one PDF page as a PNG image: use it for wiring diagrams, connector pin views, exploded views and tables that read poorly as text. Returns a short text part first (the page link, its heading and text) and then the image. If no image reaches you, your client does not pass images on: use the text, and give the user the link to see the page; asking again will not help. format="pdf" returns the page as a one-page PDF instead of the image (for clients that read PDFs but not images; ChatGPT gets it by default).

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": {
      "file": "<file>",
      "page": "<page>"
    },
    "name": "page_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
pageYes
zoomNo
formatNopng

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely non-obvious behavior: the response is a text part first (page link, heading, text) followed by the image, plus the failure mode where a client drops images and retrying is futile. The format="pdf" escape hatch and the ChatGPT default are extra operational context not derivable from structured fields.

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, front-loaded with the action and its return shape; the fallback and format notes each earn their place. The parenthetical about ChatGPT is marginally tangential but still operationally useful.

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?

No output schema exists, and the description compensates by spelling out the return payload ordering and the no-image case. What's left thin is the meaning of the `file` and `zoom` inputs for a 4-parameter tool, which keeps it from being fully self-sufficient.

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 coverage is 0%, so the description must carry the parameters, and it only fully explains `format` (png vs one-page pdf) — valuable but one of four. `zoom` (default 1.6) is never described in units or effect, and `file` is never stated as a path, id, or manual reference; `page` is self-evident. Partial compensation, not full.

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 precise verb+resource+output: "Render one PDF page as a PNG image," then scopes it to content that "reads poorly as text," which implicitly separates it from the text-extraction siblings (read_pages/get_contents). An agent knows exactly what it gets back and when this is the right renderer.

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?

Gives positive use cases (wiring diagrams, connector pin views, exploded views, tables), a fallback protocol when no image arrives (use the text, hand the user the link, don't retry), and an explicit alternative path for PDF-only clients via format="pdf". This is close to exhaustive routing guidance.

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