Skip to main content
Glama
vishnu-77

OpenReflex

by vishnu-77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Explain decision

explain_decision
Read-onlyIdempotent

Explains why OpenReflex recommended a path, pivot, or stop, including strategy, Reflex Score, success probability, confidence, signals, next-best option, and policy version.

Instructions

Explain OpenReflex's latest recommendation for the most recent task. Returns: plain text with the recommended strategy, the Reflex Score (0-100: how strong the recommendation is, not the chance of success), the estimated success probability, confidence, the signals behind the score, the next-best strategy with its route advantage, and the policy version. Use when: the user asks why OpenReflex suggested a path, pivot or stop. Not for: the same numbers as structured data (use get_reflex_score) or every decision in order (use get_execution_trace). Side effects: none; read-only. Errors: 'No decision snapshot recorded yet' before any task was planned; a 'not enabled' message until the project is approved.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.2

TDQS

A4.9/5.0
Behavior5/5

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

The description adds behavioral context beyond annotations: it explicitly states 'Side effects: none; read-only' and discloses specific error messages ('No decision snapshot recorded yet', 'not enabled'). It also clarifies that the Reflex Score is a recommendation strength, not success probability, which is a valuable interpretive detail.

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?

The description is well-structured with labeled sections ('Returns', 'Use when', 'Not for', 'Side effects', 'Errors') that front-load the most important information. Every sentence adds distinct value, and the length is justified by the rich behavioral and error context.

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

Completeness5/5

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

Given the zero-parameter input and the presence of an output schema, the description fully covers what an agent needs: what is returned, when to use it, exclusions, side effects, and error conditions. No gaps are apparent for safe and correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the description need not explain parameter semantics. The schema coverage is 100% and there is nothing to add; the baseline of 4 is appropriate.

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?

The description uses a specific verb ('Explain') and resource ('OpenReflex's latest recommendation for the most recent task'), clearly stating the tool's scope. It also distinguishes itself from siblings by explicitly naming get_reflex_score and get_execution_trace as alternatives for structured numbers or chronological decisions.

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

Usage Guidelines5/5

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

The description provides explicit 'Use when' and 'Not for' sections, giving clear conditions for invocation and excluding the sibling tools. It leaves no ambiguity about when to choose this tool over the alternatives.

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

Deploy Server

Other Tools