ltspice-mcp

by xuio

Overview Schema Source Related Servers Discussions Admin

Python

Local

startLtspiceRenderSession

Opens an LTspice window once, then renders images repeatedly without reopening.

Instructions

Open an LTspice window once for repeated image rendering.

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": {
      "path": "<path>"
    },
    "name": "startLtspiceRenderSession"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`title_hint`	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 are provided, so the description must disclose behavioral traits. It only says 'Open an LTspice window once,' omitting critical details such as whether the session must be ended via 'endLtspiceRenderSession', whether it modifies global state, or if multiple sessions are allowed. The tool's side effects and lifecycle are not explained.

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, front-loaded sentence that efficiently communicates the core action but is too sparse to cover necessary details. While concise, it sacrifices completeness for brevity.

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

Completeness1/5

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

Given the tool has two parameters with no schema descriptions, no annotations, and an output schema (not shown), the description is severely incomplete. It fails to explain parameter semantics, usage prerequisites, session lifecycle, or behavior, making it nearly unusable for an AI agent without external knowledge.

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 does not mention either parameter ('path' or 'title_hint'). The agent has no indication of what 'path' refers to (e.g., file path, directory) or how 'title_hint' affects behavior. The description adds zero value beyond the schema's bare structure.

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?

The description states 'Open an LTspice window once for repeated image rendering,' which clearly identifies the action (open a window) and the resource (LTspice window) with a specific purpose (repeated image rendering). It distinguishes from siblings like 'openLtspiceUi' (general UI open) and 'endLtspiceRenderSession' (session end), though the phrase 'repeated image rendering' is somewhat vague.

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 like 'openLtspiceUi' or prerequisites such as needing a session before rendering. No exclusions or explicit context is given, leaving the agent unsure about proper invocation sequence.

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

Deploy Server