Skip to main content
Glama
Sign In
ltspice-mcp

ltspice-mcp

by xuio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

getPlotNames

List plot names from LTspice RAW files. Provide a run ID or raw path to access available simulation data plots.

Instructions

List LTspice plot names available in one RAW file or all RAW files from a run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getPlotNames"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idNo
raw_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.32.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states that the tool lists plot names, which implies a read-only operation, but does not disclose any potential side effects, permissions needed, or limitations. It is minimally transparent.

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?

The description is a single, concise sentence that conveys the core purpose without extraneous words. It is well-structured and front-loaded.

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?

Given the tool has two optional parameters and an output schema (not shown), the description is brief but adequate for a simple listing operation. However, it lacks explanation of how run_id and raw_path relate, and does not specify what plot names are or how they are returned, leaving some gaps for an agent unfamiliar with LTspice.

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?

The input schema has 0% description coverage, meaning the description must explain the parameters. The description mentions 'RAW file' and 'run' but does not explicitly map to the parameters run_id and raw_path. The agent cannot infer the parameter meanings without additional context.

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 action (list), the resource (LTspice plot names), and the scope (in one RAW file or all RAW files from a run). It distinguishes from sibling tools like getVectorsInfo which list vector names, not plot names.

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 when to use the tool (to list plot names from RAW files), but does not explicitly provide when-not-to-use or mention alternative tools. It is adequate for basic guidance but lacks depth for complex decisions.

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