Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_get_refinement

Retrieve a refinement audit record by ID to review the change, supporting evidence, and outcome for verification or rollback decisions.

Instructions

Inspect a refinement audit record.

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_get_refinement"
  }
}

Input Schema

NameRequiredDescriptionDefault
refinement_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read operation but does not disclose permissions, whether audit records are immutable, error behavior for missing IDs, or what the response contains.

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?

The description is a single front-loaded sentence with no wasted wording. Its brevity is appropriate structurally, though it leaves important details unstated.

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 simple one-parameter lookup tool, the definition is still too thin: it lacks annotations, an output schema, and any explanation of the returned audit record. An agent would know the basic action but not what to expect from the result.

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?

The single parameter refinement_id has 0% schema description coverage, and the description adds no meaning about its format, source, or expected values. It only implies that the ID identifies a refinement audit record.

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: "Inspect" a "refinement audit record." This distinguishes it from the mutating sibling reflex_apply_refinement, though it does not explicitly name alternatives.

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?

There is no guidance on when to use this tool versus alternatives such as reflex_list_proposals or reflex_apply_refinement. The read-only intent is only implied by "Inspect."

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