ltspice-mcp

simulation_summary

Read-onlyIdempotent

Retrieve a complete simulation summary covering analysis type, signals, data size, .MEAS results, Fourier analysis, AC bandwidth metrics, and warnings to verify circuit behavior.

Instructions

Get a comprehensive simulation summary including type, signal list, data size, .MEAS results, Fourier analysis, AC bandwidth metrics, and warnings.

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": "simulation_summary"
  }
}

Input Schema

Name	Required	Description
`step`	No	Step index for ac_bandwidth_metrics on a stepped (.step) run. Default 0 (first step). On a multi-step run the metric is computed for this step only — a warning notes it.
`format`	No	Response format: 'json' for structured data, 'text' for human-readable
`job_id`	No	Summarize a specific run of a completed sweep/MC (or single) job instead of a raw_file path; pair with ``run_index``. The .log is taken from beside the run's raw unless ``log_file`` is given.
`signal`	No	Signal for AC bandwidth metrics (e.g., 'V(outp)'). Required for AC analysis.
`log_file`	No	Optional path to .log file. Defaults to the resolved raw with the extension swapped to ``.log`` — pass an explicit value only if the log lives somewhere unusual.
`raw_file`	No	Path to .raw result file. Pass this OR ``job_id`` (a job run), not both.
`run_index`	No	0-based run to summarize when ``job_id`` is given (default 0).

Output Schema

Name	Required	Description	Default
`range`	No
`errors`	No
`fourier`	No
`signals`	No
`sim_type`	No
`warnings`	No
`step_count`	No
`meas_errors`	No
`point_count`	No
`measurements`	No
`observations`	No
`failed_measurements`	No
`ac_bandwidth_metrics`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the list of report sections but no extra behavioral context (e.g., performance for large files, reliance on job_id vs raw_file). With annotations present, a 3 is appropriate.

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, focused sentence that front-loads the core action and lists key outputs. No extraneous words or repetition; it earns its place.

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

Completeness4/5

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

With a present output schema, full parameter descriptions, and safety annotations, the description is sufficient for a summarization tool. It covers all major report components, and the agent can infer that no side-effects occur. Slight miss: no mention of the job_id/raw_file choice, but that is schema-documented.

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

Parameters3/5

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

Schema coverage is 100% – every parameter has a detailed description in the input schema. The tool description does not add any parameter-level meaning beyond what the schema already provides, so the baseline 3 applies.

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 uses a specific verb ('Get') and resource ('comprehensive simulation summary') and enumerates the exact contents (type, signal list, data size, .MEAS results, Fourier analysis, AC bandwidth metrics, warnings). This clearly differentiates it from siblings like bode_metrics or thd, which target specific analyses.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., batch_results, check_job). It does not mention prerequisites, workflows, or exclude cases. Given the rich sibling set, this is a notable gap.

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