Skip to main content
Glama
SpiceMCP
by oniondas

rollback_to_candidate

Restore a past candidate’s exact netlist from storage and return its file path, avoiding rebuilding an old circuit from memory.

Instructions

Restore a past candidate's exact netlist from storage and return its file path. Use this instead of rebuilding an old circuit from memory.

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>",
      "candidate_id": "<candidate_id>"
    },
    "name": "rollback_to_candidate"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
candidate_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose some meaningful behavior: the netlist comes from storage, it is the 'exact' past version, and the tool returns a file path rather than a netlist body. What's missing is the side-effect profile, namely whether restoring replaces or overwrites the current design state and whether any auth or run-state prerequisite applies to a mutation-shaped operation.

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 sentences, both earning their place: the first declares the action and return artifact, the second gives usage direction. Front-loaded and free of filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, no-annotation, no-output-schema tool, the definition covers the core action and the return artifact, which is good. But it leaves both parameter meanings and the state-changing side effects undocumented, so an agent could invoke it without knowing what run_id scopes or what happens to the current design.

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% for two required parameters. The description implies candidate_id selects a past candidate, but it says nothing about run_id, its relationship to candidate_id, or format expectations. With both identifiers undocumented in the schema, the description should have compensated and does not.

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 specific verb and resource: restore a past candidate's exact netlist from storage. It also mentions the return value (the file path), so the agent knows what artifact it gets back. It doesn't distinguish this tool from sibling tools such as evaluate_candidate or render_schematic, but the operation itself is unambiguous.

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 line 'Use this instead of rebuilding an old circuit from memory' gives usage context: it tells the agent to retrieve a stored candidate instead of reconstructing it. However, it gives no preconditions (run_id validity, candidate existence), no exclusions, and no direction to any sibling tool, so the guidance is implied rather than explicit.

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