Skip to main content
Glama
SpiceMCP
by oniondas

render_schematic

Generates PNG or SVG schematics from LTspice .asc files or SPICE netlists, automatically placing, routing, and checking the circuit before rendering.

Instructions

Draw a schematic as PNG or SVG. path: an LTspice .asc, or a SPICE netlist (.cir/.net/.sp), which is auto-placed, routed and checked first.

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": {
      "path": "<path>"
    },
    "name": "render_schematic"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
styleNotech_minimal
output_pathNoschematic.png

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It usefully discloses that netlist inputs are auto-placed, routed and checked first, but says nothing about the fact that it writes a file to output_path, whether an existing file is overwritten, what happens on placement/routing failure, or how the result is returned.

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?

Two sentences, front-loaded with the verb, resource and output formats, then the input constraint. No filler and nothing buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a rendering tool with no annotations and no output schema, the description covers the input contract but leaves two parameters unexplained and the return channel ambiguous — it is unclear whether an inline image or a path on disk is produced, which is the main thing an agent needs to know here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 compensate. It explains `path` well (three accepted netlist extensions plus .asc), but `style`'s three enum values and `output_path` (including its default) get no meaning at all — two of three parameters remain undocumented in both the schema and the description.

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?

Specific verb plus resource plus output media: "Draw a schematic as PNG or SVG." That is well beyond a tautology and lets an agent distinguish rendering from siblings like simulate or check_feasibility, though it never names a sibling to contrast with.

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?

Usage is implied rather than stated: the accepted input types (.asc or SPICE netlist) tell an agent what it must already have, but there is no explicit when-to-use, no when-not-to-use, and no named alternative for e.g. producing a report instead of a drawing.

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