kicad-mcp-layer

Overview Schema Source Related Servers Discussions Admin

doc_page

Idempotent

Renders a PDF page to an image for pinout drawings, package dimensions, and tables that text extraction cannot handle. Use when datasheet visuals must be inspected.

Instructions

Render one page of a PDF to an image and return it, for pinout drawings, package dimensions, tables and anything else text extraction cannot carry.

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": {
      "doc": "<doc>",
      "page": "<page>"
    },
    "name": "doc_page"
  }
}

Input Schema

Name	Required	Description
`doc`	Yes	Document id, library file name, title, or a path inside the workspace.
`page`	Yes
`scale`	No	Render scale; 2 is about 144 dpi.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description usefully adds that the return value is image data rather than text, but says nothing about output limits, page-range constraints, or why readOnlyHint is false for a render operation. Adequate but not rich.

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

Conciseness5/5

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

A single sentence, front-loaded with the action and its result, then the use cases. No filler, no restatement of the tool name or schema.

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?

With no output schema, the description must signal the return type, and it does ('return it [an image]'). Combined with the annotation profile and a fairly well-described schema, an agent has enough to call it correctly; only edge details like resolution limits remain unstated.

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 67%: 'doc' enumerates its accepted forms (id, file name, title, path) and 'scale' documents the 144 dpi reference point. The description adds nothing about 'page' numbering or scale trade-offs, so the schema does the heavy lifting. Baseline 3 is appropriate.

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 ('Render one page of a PDF to an image and return it') and immediately carves out its niche by contrasting with the sibling doc_text: for content 'text extraction cannot carry.' An agent can distinguish it from doc_text, doc_fetch and doc_sections without opening any 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?

Gives clear usage context — pinout drawings, package dimensions, tables, anything text extraction misses — which effectively routes the agent away from doc_text toward this tool. It stops short of an explicit 'use X instead when Y' statement, but the selection condition is unambiguous.

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