Skip to main content
Glama
Sign In
LTspice MCP

LTspice MCP

by kh6570
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Prepare Dc Sweep

prepare_dc_sweep

Inserts a .dc directive to set up a DC sweep analysis in LTspice, defining the source, start, stop, and step values.

Instructions

Insert a .dc directive.

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>",
      "source": "<source>",
      "start": "<start>",
      "stop": "<stop>",
      "step": "<step>"
    },
    "name": "prepare_dc_sweep"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepYes
stopYes
startYes
sourceYes
schematic_pathYes
workspace_rootNoOptional per-call workspace root override.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already disclose readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — it does not say whether the directive is appended to an existing netlist, whether repeated calls duplicate directives (idempotentHint=false), or what a successful insertion returns. Almost no value beyond structured fields.

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?

One short sentence with no wasted words and the action front-loaded, but the brevity is under-specification rather than economy — it omits information the agent needs. Not verbose, just incomplete.

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

Completeness1/5

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

A six-parameter, five-required mutation tool with no output schema and no parameter documentation needs the description to carry the load. It delivers a single jargon sentence, leaving the sweep syntax, the effect on the target file, and the return behavior all unspecified.

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 only 17% — five required parameters (schematic_path, source, start, stop, step) are bare strings with no documentation, and the description explains none of them. Critically, the expected syntax for SPICE sweep values (e.g., '1m', '10k', 'dec/oct/lin') is left entirely ambiguous, which will cause incorrect calls.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Insert' plus the target 'a .dc directive' does identify the action, but '.dc' is SPICE jargon that is never unpacked, and nothing distinguishes this from sibling preparation tools such as prepare_ac, prepare_transient, or prepare_temperature_sweep. The name carries most of the meaning; the description essentially restates it in shorthand.

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?

There is no guidance on when to use this versus the many other prepare_* directive tools, nor any statement of prerequisites (e.g., that a netlist/schematic must already exist) or what to do next. The agent must infer everything from the tool name.

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

Deploy Server

Other Tools