ltspice-mcp

by xuio

Overview Schema Source Related Servers Discussions Admin

Python

Local

scanModelIssues

Scan LTspice simulation logs to detect missing models, includes, or subcircuits, and get suggestions for resolution.

Instructions

Scan LTspice log text for missing model/include/subcircuit issues.

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

Input Schema

Name	Required	Description	Default
`run_id`	No
`log_path`	No
`search_paths`	No
`suggest_matches`	No
`max_scan_files`	No
`max_suggestions_per_issue`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.32.0Jun 10, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations provided; description only states the action but does not disclose behavioral details such as side effects, read-only nature, or dependencies. For a scanning tool, more transparency is needed.

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?

The description is a single short sentence, which is concise but fails to provide necessary detail given the tool's 6 parameters. It front-loads the core action but is too sparse.

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?

Despite having an output schema, the description does not cover how to use the parameters or the expected behavior. For a tool with 6 parameters and no schema descriptions, it is incomplete.

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%, and the description adds no meaning to any of the 6 parameters. Parameters like run_id, log_path, search_paths are not explained, requiring the agent to infer from names.

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?

Description clearly states it scans LTspice log text for missing model/include/subcircuit issues. It specifies a specific action and resource, distinguishing it from sibling tools that deal with measurements or other aspects.

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 explicit guidance on when to use this tool vs alternatives. Does not describe prerequisites or conditions for use, leaving the agent to infer context.

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

Deploy Server