Skip to main content
Glama
SpiceMCP
by oniondas

check_feasibility

Verifies whether a circuit spec is physically achievable before simulation, using goals, limits, and technology values without requiring LTspice or a netlist.

Instructions

Check if a spec is physically possible before simulating. Free, no LTspice. Use mode="concept" without a netlist; tech holds SI values like vdd, cload, vin.

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": {
      "goals": "<goals>"
    },
    "name": "check_feasibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNopractical
techNo
goalsYes
limitsNo
paramsNo
netlistNo
circuit_typeNogeneral

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description does useful work by disclosing cost and side effects: 'Free, no LTspice' tells the agent no simulator is spun up and the call is cheap. It never says what the check returns (a verdict, a margin, a diagnostic list) or whether it is advisory versus blocking, which is the main behavioral gap for a pre-flight validation tool.

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, front-loaded with the core purpose and the cost guarantee, then the mode/netlist rule. Nothing is wasted or repeated from the schema.

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?

This is a complex tool: seven parameters, nested Goal/Limit/Param objects, no annotations, and no output schema. The description covers only the mode/netlist interaction and the tech dictionary, saying nothing about what a feasibility result looks like or how goals/limits/params shape the verdict, so it is under-specified for the tool's complexity.

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 0% at the top level, so the description must compensate, and it partially does: it explains that tech carries SI values with concrete examples (vdd, cload, vin) and that mode="concept" pairs with an empty netlist — a coupling the schema does not express. However, goals, limits, params, and circuit_type receive no explanation, leaving most of the seven parameters undocumented.

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?

States a specific verb and object ('Check if a spec is physically possible') and scopes it in time ('before simulating'), which separates it from the simulate sibling. It stops short of naming an alternative tool explicitly, but the boundary is inferable.

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?

Gives a clear precondition ('before simulating') plus a concrete routing rule: use mode="concept" when there is no netlist. It does not say when to skip this check entirely or when practical/theoretical modes are preferable, so it is context-rich but not exhaustive.

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