ltspice-mcp

Overview Schema Source Related Servers Discussions Admin

createSchematic

Create LTspice .asc schematics from structured component, wire, and directive data. Automate circuit layout generation with custom parameters.

Instructions

Create an LTspice .asc schematic from structured component/wire/directive data.

Components must include: symbol, reference, x, y. Optional component fields: value, orientation|rotation, attributes, pin_nets.

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": {
      "components": "<components>"
    },
    "name": "createSchematic"
  }
}

Input Schema

Name	Required	Default
`components`	Yes
`wires`	No
`directives`	No
`labels`	No
`circuit_name`	No	schematic
`output_path`	No
`sheet_width`	No
`sheet_height`	No
`open_ui`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.32.0Jun 10, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It does not mention side effects (e.g., file creation), validation behavior, or outcome. The existence of an output schema partially mitigates, but the description adds no behavioral context.

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?

The description is concise, with two sentences front-loading the core purpose. However, it could be more structured by listing all parameters or grouping optional ones.

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

Completeness2/5

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

Given the complexity (9 parameters, no schema descriptions, no annotations), the description covers only the components parameter. Important details like output path, sheet size, and UI behavior are missing. Incomplete for effective tool selection.

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 coverage is 0%, so description must compensate. It only describes the components parameter (required and optional fields), leaving the other 8 parameters (wires, directives, labels, circuit_name, output_path, sheet dimensions, open_ui) entirely undocumented. This is insufficient for a 9-parameter tool.

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?

The description clearly states the tool creates an LTspice .asc schematic from structured component/wire/directive data, specifying required and optional component fields. However, it does not explicitly distinguish itself from sibling tools like createSchematicFromNetlist or createSchematicFromTemplate, which have different input sources.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, no prerequisites, no scenarios. The description only states what the tool does but not the context for choosing it.

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

Deploy Server