Skip to main content
Glama
SpiceMCP
by oniondas

check_setup

Displays the active LTspice path and project folder to confirm the simulation setup and help diagnose failures before troubleshooting.

Instructions

Show the LTspice path and project folder in use. Call first if anything fails to simulate.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. 'Show' reasonably implies a read-only operation and it states what information is surfaced, but it does not explicitly confirm there are no side effects, nor does it describe permissions or what the response looks like.

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?

Two short sentences, the output content is front-loaded and the usage cue follows immediately. There is no filler and every clause carries information.

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

Completeness4/5

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

For a zero-parameter diagnostic with no output schema, the agent needs to know what is returned and when to reach for it, and both are covered. Only minor gaps remain around confirming it is a pure read with no side effects.

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 takes zero parameters, so the schema has nothing to explain and there is no parameter behavior for the description to compensate for. Baseline for a parameterless tool applies.

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 pairs a specific verb ('Show') with specific resources ('the LTspice path and project folder in use'), so an agent knows this is an environment/diagnostic inspection tool. It does not name or contrast with siblings like check_feasibility, but the payload named is distinctive enough to separate it from simulate or find_part.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger condition: 'Call first if anything fails to simulate,' which tells the agent when this tool is the right choice. It stops short of stating when not to call it (e.g. proactively before a run) or naming a follow-up alternative.

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