Skip to main content
Glama
Sign In
ltspice-mcp

ltspice-mcp

by xuio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

endLtspiceRenderSession

Close a specific LTspice render session window to free system resources and complete the rendering task.

Instructions

Close the LTspice window associated with a render session.

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": {
      "render_session_id": "<render_session_id>"
    },
    "name": "endLtspiceRenderSession"
  }
}

Input Schema

NameRequiredDescriptionDefault
render_session_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.32.0

TDQS

C2.6/5.0
Behavior2/5

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

The description indicates a destructive action (closing a window) but does not disclose side effects, such as whether unsaved changes are handled or if resources are released. With no annotations, the burden is higher, and the description is insufficient.

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 very concise at 11 words, but it sacrifices essential details like usage context and parameter hints. It is front-loaded but not sufficiently informative.

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?

Given the tool's role in ending a stateful session, the description omits prerequisites, return values (no output schema provided), and relations to other tools like 'startLtspiceRenderSession'. It is incomplete for a mutation tool with no annotations.

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 sole parameter 'render_session_id' is not elaborated in the description. Schema coverage is 0%, so the description should explain what a render session ID is and how it is obtained, but it adds no value beyond the parameter's name.

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 clearly states the action (close) and the resource (LTspice window associated with a render session). It is specific and distinguishable from siblings like 'closeLtspiceWindow' by its focus on render sessions, though it does not explicitly differentiate.

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 guidance is provided on when to use this tool versus alternatives such as 'closeLtspiceWindow'. The description lacks context, e.g., it should mention that the render session must be active or that the session ID comes from 'startLtspiceRenderSession'.

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