Skip to main content
Glama
SpiceMCP
by oniondas

start_from_template

Build and simulate a run from a ready-made circuit template, sizing it with hand equations and optional part substitutions to establish a starting point for optimization.

Instructions

Build a run from a ready-made circuit, size it by hand equations and simulate that start point. spec keys from list_templates (SI); parts: names from find_part.

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>",
      "template": "<template>",
      "spec": "<spec>"
    },
    "name": "start_from_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes
partsNo
run_idYes
templateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose one important trait — this call simulates the starting point rather than just registering a design — but it never explains whether run_id identifies an existing run or is created here, what side effects occur, whether the operation is reversible, or what a failure 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.

Conciseness4/5

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

Two short sentences with no filler, and the core action is stated first. The parenthetical '(SI)' and 'size it by hand equations' are terse to the point of ambiguity, but nothing is wasted.

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 — four parameters, nested objects, three required inputs, no annotations and no output schema — yet the description covers only how to source spec and parts. It omits the meaning of run_id and template, the simulation side effects, and what the caller receives, which is not enough for an agent to invoke it confidently.

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%, so the description must compensate, and it partially does: spec is sourced from list_templates with SI units, and parts takes names from find_part (matching the opamp/switch/diode keys visible in the schema). The two remaining required parameters, run_id and template, get no meaning at all, leaving a significant gap for a nested-object tool.

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 gives a concrete verb phrase — 'Build a run from a ready-made circuit' — plus the additional behavior that the start point is sized by hand equations and simulated, which distinguishes it from a bare run-creation tool. It also names two sibling tools it depends on (list_templates, find_part), although the phrase 'size it by hand equations' is domain jargon that is not self-explanatory.

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?

There is useful procedural guidance: spec keys come from list_templates in SI units, and part names come from find_part, which tells the agent how to prepare the call. However, there is no statement of when to prefer this over other entry points such as start_optimization or check_feasibility, and no preconditions (e.g., whether run_id must already exist).

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