Skip to main content
Glama
SpiceMCP
by oniondas

query_run

Retrieve saved circuit simulation run data to inspect status, candidates, netlists, and detailed results. Use it to review optimization history and choose next steps.

Instructions

Read saved run data. Default what="status". "runs" lists runs; "details" = hand calc, warnings, alternatives. candidate/netlist/similar need candidate_id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "query_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
whatNostatus
limitNo
metricNo
run_idNo
parameterNo
candidate_idNo
candidate_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and it only implicitly signals a safe read via "Read saved run data". It says nothing about behavior when run_id is absent, what the limit ceiling does, whether results are truncated, or how modes behave with no prior run -- all material for a tool with seven parameters.

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?

Three short sentences, front-loaded with the core action and the default mode, with no filler. The telegraphic phrasing ("hand calc", "similar") is terse almost 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?

For a seven-parameter, fifteen-mode tool with no annotations and no output schema, this description is substantially incomplete -- most modes and most parameters are undocumented, leaving an agent unable to choose a mode beyond status/runs/details or to predict what comes back.

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 was required to compensate and only partly does: it documents the `what` default and three or four of fifteen enum values, plus the candidate_id dependency. The limit, metric, run_id, parameter, and candidate_ids parameters, and eleven enum values including best/pareto/history/trace/next/sensitivity/explored, receive no explanation anywhere.

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?

"Read saved run data" is a specific verb plus resource, and the mode names ("runs", "details") make clear this is a read/inspection tool rather than a mutating sibling like simulate or run_optimization. It stops short of a 5 because the tool is a 15-mode multiplexed query and only two modes are characterized, so an agent cannot fully distinguish what this tool covers.

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?

The description supplies genuine prerequisites -- candidate/netlist/similar modes require candidate_id -- and states the default mode, which is real conditional guidance. However it names no alternative tool and gives no when-to-use/when-not-to-use framing against siblings such as evaluate_candidate or check_feasibility, and the majority of the 15 modes have no usage context at all.

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