Skip to main content
Glama
SpiceMCP
by oniondas

run_optimization

Runs multiple LTspice simulations from one request and returns one optimization summary, so you can tune circuit parameters without manually looping candidate evaluations.

Instructions

Let the server search for iterations simulations and return one summary. Preferred way to optimize: do not loop evaluate_candidate yourself.

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

Input Schema

NameRequiredDescriptionDefault
run_idYes
iterationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description still discloses two important behaviors: the loop happens server-side and the result is a single aggregated summary rather than per-candidate output. It omits whether the call blocks for a long time, whether it mutates run state, and what happens on invalid or unauthorised `run_id`.

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, no filler, with the core action first and the anti-pattern warning second. Nothing could be removed without losing information.

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?

No annotations and no output schema mean the description is the only behavioral source, yet it leaves the required `run_id` unexplained and says nothing about duration, side effects, or failure modes of what may be a long-running optimization call.

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 description coverage is 0%, so the description must carry parameter meaning. It does explain that `iterations` is the number of simulations to run, but never mentions the default of 20, the 1-500 bounds, or the meaning and provenance of the required `run_id`.

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 states a concrete action (the server runs `iterations` simulations) and an output shape (one summary), which is more than a restatement of the name. It also explicitly contrasts itself with the `evaluate_candidate` sibling, so an agent can tell the two apart.

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?

It gives a direct recommendation: prefer this tool over manually looping `evaluate_candidate`. It falls short of full 5 because it does not state prerequisites (that a `run_id` must first come from `start_optimization`) or when not to use it.

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