Skip to main content
Glama
Sign In
ltspice-mcp

ltspice-mcp

by xuio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

getRecentErrors

Scan recent daemon logs and extract structured error entries for troubleshooting LTspice simulations.

Instructions

Scan recent daemon logs and return structured error entries.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
log_countNo
include_warningsNo
log_dirNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.32.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It implies a read operation but does not state whether it modifies state, how recent logs are scanned, or any side effects. Lacks details on permissions or limitations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the core purpose. However, it could be slightly more structured by separating the action and output for even clearer scanning.

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?

The tool has an output schema, but the description does not clarify what constitutes an 'error entry' or the time range. Given four parameters go undocumented and no behavioral context, the description is incomplete for effective use.

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%: the description does not mention any of the four parameters (limit, log_count, include_warnings, log_dir). It adds no meaning beyond what the schema provides, which already has defaults but no descriptions.

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 scans recent daemon logs and returns structured error entries. It specifies the verb 'scan' and resource 'daemon logs', and the output is structured error entries, which distinguishes it from sibling tools like tailDaemonLog that return raw logs.

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 on when to use this tool versus alternatives like tailDaemonLog or daemonDoctor. The description does not mention prerequisites, exclusions, or context for choosing this tool.

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