ltspice-mcp

by xuio

Overview Schema Source Related Servers Discussions Admin

Python

Local

generatePlotPresetSettings

Creates deterministic .plt settings for a named plot preset in LTspice simulations, ensuring consistent waveform views.

Instructions

Generate deterministic .plt settings for a named preset.

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": {
      "preset": "<preset>"
    },
    "name": "generatePlotPresetSettings"
  }
}

Input Schema

Name	Required	Description	Default
`preset`	Yes
`vectors`	No
`plot`	No
`run_id`	No
`raw_path`	No
`step_index`	No
`output_path`	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

Behavior2/5

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

No annotations provided, so description carries full burden. It mentions 'deterministic' but does not disclose side effects, permissions, or whether it modifies state. The output schema exists but is not referenced.

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?

Single sentence, no wasted words, front-loaded. However, it is too short given the parameter complexity, but conciseness is not penalized for lack of detail.

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?

With 7 parameters, 0% schema coverage, and no annotations, the description lacks context for optional parameters and does not clarify when to set them. Output schema exists but is not leveraged.

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% (only titles). The description does not explain any parameter beyond the name 'preset', leaving six optional parameters completely unexplained.

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 specifies the verb 'Generate', the resource '.plt settings', and the qualifiers 'deterministic' and 'for a named preset', which distinguishes it from siblings like 'generatePlotSettings'.

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 implies usage for generating .plt settings from a preset but gives no explicit guidance on when to use this vs. alternatives like 'generatePlotSettings' or when not to use it.

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

Deploy Server