Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

sim_spice

Run SPICE circuit simulations from a netlist using built-in or ngspice engines, with analysis, temperature, iteration, and cross-check options to verify PCB designs.

Instructions

...

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

Input Schema

NameRequiredDescriptionDefault
engineNo ...builtin
temp_cNo ...
netlistYes ...
analysisNo ...
max_iterNo ...
max_pointsNo ...
cross_checkNo ...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.43

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not say whether simulation executes external binaries (the 'engine' enum hints at ngspice), whether runs are expensive or long, what errors look like, or what the result contains.

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

Conciseness1/5

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

There is no content to be concise about; the single placeholder string is under-specification rather than concision. Nothing is front-loaded because nothing is stated.

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

Completeness1/5

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

This is a 7-parameter simulation tool with no annotations and no output schema, the case where the description must do the most work. Instead it is entirely blank, leaving engine selection, temperature, analysis type, and iteration limits unexplained.

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

Parameters3/5

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

Schema description coverage is nominally 100% across all 7 parameters, so the schema is nominally the source of parameter meaning and the baseline of 3 applies. The description adds nothing on top of it, and notably the schema descriptions themselves appear to be placeholder " ..." strings, so real semantics are likely absent everywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is the placeholder string " ..." and states no verb, resource, or purpose. Nothing distinguishes this tool from siblings like ir_drop_chain or decoupling_check, and an agent cannot tell it runs SPICE simulation without inferring from the tool name alone.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no exclusions, and no mention of alternatives. The description is empty, so an agent has no basis for choosing sim_spice over any other analysis tool in the catalog.

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