Skip to main content
Glama

export_schematic_svg

Export the pages of a KiCad schematic as SVG vector files using kicad-cli, rendering each sheet path as its own zoomable page for clear, lossless viewing and sharing.

Instructions

Export the pages of a schematic as SVG files with kicad-cli.

kicad-cli renders the pages of the project with the hierarchy of its root schematic (the schematic of the project name), thus each page has the references of its sheet path. For the root schematic, the files are all pages of the project. For an other file (a sub-sheet), the files are the pages of its sheet paths (a sheet that the hierarchy uses two times gives two pages). An SVG file is a vector image: a zoom shows each detail with no loss. The tool needs kicad-cli.

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": {
      "schematic_path": "<schematic_path>"
    },
    "name": "export_schematic_svg"
  }
}

Input Schema

NameRequiredDescriptionDefault
output_dirNoOptional folder of the files. Default: <schematic>_svg next to the schematic.
schematic_pathYesA .kicad_sch file of the project.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the external dependency on kicad-cli, the mapping from file hierarchy to produced pages, and the default output location. It omits what happens to pre-existing files in the output directory (overwrite/append), which is the main remaining gap for a file-emitting tool.

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?

The purpose is correctly front-loaded in sentence one, but the hierarchy paragraph is wordy and awkwardly phrased ('a sheet that the hierarchy uses two times gives two pages'). The aside 'An SVG file is a vector image: a zoom shows each detail with no loss' is filler that does not help an agent invoke the tool correctly.

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?

An output schema exists, so return values need not be described, and the description covers the prerequisite, the default output location and the hierarchical page-expansion behavior. It is nearly complete for a two-parameter export tool, lacking only file-overwrite behavior and rough output naming.

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 100%, so both parameters are already documented, making 3 the baseline. The description does add genuine meaning beyond the schema for schematic_path by explaining that a sub-sheet yields pages from its sheet paths and that repeated sheet instances multiply the output, though output_dir gets no additional semantics.

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?

The first sentence gives a specific verb ('Export'), a specific resource ('pages of a schematic') and a concrete output format ('SVG files'), plus the underlying mechanism (kicad-cli). This is clearly distinguishable from sibling exporters such as export_bom, export_gerber or export_pcb_3d, which target different artifacts.

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

Usage Guidelines3/5

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

The description explains how input selection changes output (root schematic vs sub-sheet, and that a sheet reused twice yields two pages), and states the kicad-cli prerequisite. However, it never says when an agent should choose this tool over alternatives, nor any when-not condition, leaving usage implied rather than directed.

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