Skip to main content
Glama
SpiceMCP
by oniondas

finish_design

Snap optimized circuit values to standard component series, check yield across part tolerances, supply, and temperature, and return the final parts list.

Instructions

Snap the best design to standard values, check yield over parts (R 1% C 5% L 20%), supply and temperature (templates: 5%, -40/25/85 C); return the parts list.

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": {
      "run_id": "<run_id>"
    },
    "name": "finish_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
supplyNo
temps_cNo
inductorsNoE12
resistorsNoE96
capacitorsNoE12
yield_runsNo
tolerance_pctNo
supply_tol_pctNo

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 real behavior: values are rounded/snapped to standard series, yield is evaluated over R/C/L tolerances (1%/5%/20%), supply tolerance (5% default) and temperature corners (-40/25/85 C), and a parts list is returned. It omits important traits: whether the snapped design mutates or persists the run, whether it is reversible, whether it errors on infeasible designs, and how many yield samples are run. Useful disclosure, but incomplete for a mutation-shaped tool.

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?

A single dense sentence with the primary action front-loaded and no filler; it packs defaults and return value into one line. The parenthetical clusters ('(R 1% C 5% L 20%)', '(templates: 5%, -40/25/85 C)') are terse to the point of being cryptic, slightly hurting readability beyond pure length.

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 9-parameter tool with a nested object, no annotations, no output schema and zero schema description coverage, the description covers only part of the surface. It never explains the required run_id or the run state it operates on, leaves three E-series enum parameters and yield_runs unexplained, and does not say whether the design is modified in place — gaps that matter for an agent deciding whether and how to call it.

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% across 9 parameters (including a nested tolerance object), so the description must compensate. It does supply meaningful defaults not present in the schema — tolerance_pct of R 1%/C 5%/L 20%, supply_tol_pct 5%, and temps of -40/25/85 C — which directly map to three parameters. It says nothing about the required run_id, what the inductors/resistors/capacitors E-series selectors control (or that 'none' disables snapping), or what yield_runs (default 30, max 500) means.

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 multi-step action: snap the design to standard values, run a yield check across component tolerances, supply and temperature, then return the parts list. This is clearly distinguishable from siblings like simulate or check_feasibility by its snapping/parts-list outcome. The weak spot is "the best design," which does not say which run or candidate is being snapped (presumably the run_id), leaving the object of the operation slightly ambiguous.

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?

There is no explicit statement of when to call this versus evaluate_candidate, simulate, or run_optimization, nor any prerequisite such as an optimized run being available. Usage as a terminal 'finish' step is only implied by the name and by 'return the parts list.' No when-not guidance or ordering relative to siblings is given.

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