Skip to main content
Glama
Sign In
ltspice-mcp

ltspice-mcp

by xuio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

getLtspiceStatus

Retrieve the current status of the LTspice executable and server configuration to verify readiness for simulations.

Instructions

Get LTspice executable status and server configuration.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.32.0

TDQS

A3.5/5.0
Behavior2/5

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

The description only states the tool 'gets' status, implying a read operation, but with no annotations provided, it fails to disclose any behavioral traits such as permissions required, latency, or side effects. It does not describe what the output contains beyond the vague 'status and configuration.'

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, well-structured sentence that directly conveys the tool's purpose with no redundancy or filler. It is maximally concise.

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

Completeness3/5

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

While an output schema exists to document return values, the description is minimal and does not hint at the schema's contents. Given the tool's role in a large family, additional context (e.g., what 'status' entails) would aid selection, but the absence is partially compensated by the output schema.

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

Parameters4/5

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

The tool has no parameters, so the description need not add parameter info. Baseline for zero parameters is 4, and the description appropriately acknowledges that no inputs are needed.

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 clearly states the tool returns 'LTspice executable status and server configuration,' specifying both the resource (executable status and server configuration) and the action (get). This distinguishes it from sibling status tools like getLtspiceLibraryStatus and getLtspiceUiStatus.

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. Given numerous sibling status tools (e.g., getLtspiceLibraryStatus, getLtspiceUiStatus), the description should indicate context for choice, but it does not.

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