ltspice-mcp

Overview Schema Source Related Servers Discussions Admin

createIntentCircuit

Generate LTspice schematics and netlists from intent templates for filters, amplifiers, and regulators. Returns file paths with optional validation.

Instructions

Create a circuit from high-level intent templates (filters, amplifier, regulator).

Returns schematic and sidecar netlist paths, and optionally validation payload.

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": {
      "intent": "<intent>"
    },
    "name": "createIntentCircuit"
  }
}

Input Schema

Name	Required	Default
`intent`	Yes
`parameters`	No
`circuit_name`	No
`output_path`	No
`sheet_width`	No
`sheet_height`	No
`placement_mode`	No	smart
`open_ui`	No
`validate_schematic`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.32.0Jun 10, 2026

TDQS

B3/5.0

Behavior3/5

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

The description mentions return values (schematic and sidecar netlist paths, optional validation payload) but lacks details on side effects, permissions, or whether the tool mutates state. With no annotations, the description carries the full burden but provides minimal 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 two sentences and front-loaded with the primary action. It is concise but could be more structured by separating return values from the main action.

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 tool's complexity (9 parameters, 1 required) and lack of schema descriptions, the description is insufficient. It partially covers outputs but does not explain how to use parameters like circuit_name, output_path, or placement_mode. The output schema exists but is not referenced.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no parameter-level information. It mentions 'intent templates' but does not explain the intent parameter or any other parameter (e.g., placement_mode, sheet_width). The agent is left with only parameter names and types.

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 description clearly states the tool creates a circuit from high-level intent templates, listing examples (filters, amplifier, regulator). This distinguishes it from siblings like createSchematic or createSchematicFromNetlist.

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 over alternatives. The description does not mention prerequisites or contexts where createIntentCircuit is preferred over createSchematicFromTemplate or listIntentCircuitTemplates.

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

Deploy Server