Skip to main content
Glama
SpiceMCP
by oniondas

evaluate_candidate

Simulates one exact set of parameter values in a specified LTspice run and caches repeated evaluations, letting you test a specific circuit idea before using run_optimization for searches.

Instructions

Simulate one exact set of param values inside a run (cached if repeated). Use to test your own idea; use run_optimization for searching.

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>",
      "params": "<params>"
    },
    "name": "evaluate_candidate"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
paramsYes
run_idYes

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 carries the full behavioral burden and does disclose one valuable trait: repeated identical calls are cached rather than re-executed. It says nothing about cost/runtime, whether the candidate is persisted into the run, what happens on invalid params, or how the unexplained 'force' flag interacts with the cache.

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, no filler, with the core action stated first and the sibling routing second. The parenthetical cache note is well placed, though it interrupts the main clause slightly.

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 tool with a nested params object, an undocumented 'force' flag, no annotations, and no output schema, the description is thin: the agent does not learn what a simulation returns (metrics, feasibility, score) or how to interpret a cached response. The key routing information is present, but the operational picture is incomplete.

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% across three parameters including a nested free-form object, so the description must compensate and largely does not. It implies a run identifier and a numeric parameter map through 'inside a run' and 'set of param values', but never explains 'force' or the numeric-map shape, leaving the most important semantics to guesswork.

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

Purpose5/5

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

States a concrete verb and resource: simulating one exact set of param values inside a run, with the caching caveat attached. It also explicitly distinguishes itself from run_optimization, so an agent can tell the two apart without opening either schema.

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?

'Use to test your own idea; use run_optimization for searching' gives an explicit when-to-use and names the correct alternative. It stops short of stating prerequisites (e.g. that a run must already exist) or when not to use it at all, so it falls just under fully prescriptive.

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