Skip to main content
Glama
Sign In
LTspice MCP

LTspice MCP

by kh6570
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Summarize Tolerance Analysis

summarize_tolerance_analysis
Read-onlyIdempotent

Compute min, max, and mean values from stepped traces to assess tolerance and variation across simulation runs.

Instructions

Summarize min, max, and mean of a stepped trace.

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": {
      "raw_path": "<raw_path>",
      "signal": "<signal>"
    },
    "name": "summarize_tolerance_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
signalYes
raw_pathYes
workspace_rootNoOptional per-call workspace root override.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so safety is covered. The description adds the useful fact that the output is min/max/mean (valuable since there is no output schema), but says nothing about how the trace is located or what happens on missing/large inputs.

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?

A single eight-word sentence with the operation and result front-loaded; nothing is wasted. It is arguably under-specified rather than verbose.

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?

For a 3-parameter tool with two undocumented required inputs, no output schema, and a domain-specific concept ('stepped trace'), the description is too thin. The output fields are mentioned, but input semantics and usage context are not.

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?

Schema description coverage is 33% – only workspace_root is documented, while the required raw_path and signal have no schema descriptions. The description does not explain what raw_path points to or how signal is specified, so it fails to compensate for the coverage gap.

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

Purpose4/5

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

States a specific verb (summarize) and resource (stepped trace) plus the computed statistics, which gives the agent a concrete sense of the operation. It does not differentiate itself from the other summarize_* siblings (summarize_batch, summarize_device_operating_points), so it falls short of a 5.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as read_waveform or measure_waveform. An agent can only infer that this follows a step sweep from the word 'stepped'.

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