Skip to main content
Glama
SpiceMCP
by oniondas

simulate

Runs a single LTspice netlist and returns its .meas results without saving state; optionally sweep one parameter by setting sweep_param and sweep_values.

Instructions

Run one netlist now and return its .meas results. Nothing is saved. To sweep, set sweep_param ("R1", "{GAIN}" or "temp") and sweep_values.

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": {
      "netlist": "<netlist>"
    },
    "name": "simulate"
  }
}

Input Schema

NameRequiredDescriptionDefault
netlistYes
timeout_sNo
sweep_paramNo
sweep_valuesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the most important trait: "Nothing is saved," making this an ephemeral, non-persisting operation. It does not cover timeout behavior (a timeout_s parameter exists with a 120s default but is never mentioned), failure modes, or whether a sweep returns one result set or many.

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?

Two short sentences, front-loaded with the core action and the no-save caveat before the sweep detail. Nothing is wasted, though the extreme terseness leaves the required netlist argument unexplained.

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?

For a four-parameter tool with no annotations, no output schema, and 0% schema coverage, the definition is thin. It conveys the return payload (.meas results) and the ephemerality, but an agent still cannot tell what format a netlist takes, what happens on timeout, or how sweep output is structured.

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?

Schema coverage is 0%, so the description must compensate for all four parameters. It does add real meaning for sweep_param by giving example values ("R1", "{GAIN}", "temp"), but the required netlist parameter and timeout_s are completely undefined, and the relationship between sweep_param and sweep_values is only sketched.

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?

"Run one netlist now and return its .meas results" gives a specific verb (run), a specific resource (a single netlist), and a stated return type (.meas results), which distinguishes it from batch/persisted siblings like query_run or run_optimization. It stops short of naming any sibling explicitly, so the boundary is implied rather than stated.

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

Usage Guidelines3/5

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

The definition gives one concrete usage rule: to sweep, set sweep_param and sweep_values. That is genuinely useful routing information, but there is no guidance on when to use this instead of check_feasibility, evaluate_candidate, or run_optimization, and no prerequisites are stated.

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