Skip to main content
Glama
Sign In
ltspice-mcp

ltspice-mcp

by xuio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

daemonDoctor

Run daemon and system health checks to get actionable recommendations for LTspice on macOS.

Instructions

Run a daemon/system health check and return actionable recommendations.

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

Input Schema

NameRequiredDescriptionDefault
include_recent_warningsNo
deep_checksNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.32.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It does not mention whether the operation is destructive, long-running, or requires permissions, only stating the function.

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 concise (one sentence), but it omits essential information, making it under-specified rather than efficiently 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?

Despite a possible output schema, the description lacks context on what the health check entails, the format of 'actionable recommendations', and how this tool relates to siblings like getCaptureHealth or getRecentErrors.

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 coverage is 0% and the description does not explain the two boolean parameters (include_recent_warnings, deep_checks) at all. The agent must infer meaning from names alone.

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 verb 'run' and the resource 'daemon/system health check' with an outcome of returning recommendations. It is distinct from siblings like getCaptureHealth or getRecentErrors, but lacks detail on what exactly is checked.

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 or when to avoid it. The description is a single sentence with no context or prerequisites.

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