Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_rollback

Revert a refinement to its stored snapshot using the refinement ID, restoring prior agent behavior when a change causes issues.

Instructions

Rollback a refinement using its snapshot

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": {
      "refinement_id": "<refinement_id>"
    },
    "name": "reflex_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
refinement_idYesRefinement ID to rollback

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and largely drops it. 'Using its snapshot' hints that a snapshot must pre-exist, but nothing is said about whether later refinements are discarded, whether the operation is reversible, or what happens if no snapshot exists for the given ID.

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?

One front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification rather than optimal sizing for a destructive operation.

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 mutating rollback tool with no annotations and no output schema, the definition is too thin: it says neither what the rollback restores nor what the caller gets back or which errors to expect. An agent could invoke this correctly by name alone, but not 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?

There is a single parameter with 100% schema description coverage, so the schema already explains that refinement_id identifies the refinement to rollback. The description adds nothing beyond that, which is acceptable at the baseline for full schema coverage.

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?

States a specific verb (rollback) with a specific resource (a refinement) and the mechanism (its snapshot), which is more than a restatement of the name. It does not, however, differentiate itself from close siblings like reflex_apply_refinement or reflex_snapshot.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no preconditions (e.g. that a snapshot must already exist), and no mention of alternatives or when not to roll back. The agent must infer the entire usage context.

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