OpenReflex

Overview Schema Source Related Servers Discussions Admin

Get Reflex Score

get_reflex_score

Read-onlyIdempotent

Retrieve the latest decision's Reflex Score and machine-readable metrics, including success probability, strategy, and evidence. Use when your program needs inspectable decision numbers without parsing prose.

Instructions

Return the latest decision's Reflex Score and machine-readable components. Returns: structured fields for availability, Reflex Score (0-100 recommendation strength, not success probability), success probability, confidence, strategy, next-best strategy, route advantage, evidence, context cost, budget use, component signals and policy version. If no decision exists, available=false and reason explains why. Use when: a program or agent needs decision numbers it can inspect without parsing prose. Not for: a readable explanation (use explain_decision) or the full decision timeline (use get_execution_trace). Side effects: none; read-only. Errors: an MCP error is returned until the project is approved.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`reason`	No	Why no score is available, when available is false.
`signals`	No	Normalised component signals used to compute the Reflex Score.
`strategy`	No	Recommended strategy for the latest decision.
`available`	Yes	Whether a decision snapshot is available for the most recent decided task.
`budget_used`	No	Largest fraction of the task budget consumed across time, calls and context.
`reflex_score`	No	Strength of the recommendation on a 0-100 scale; not success probability.
`context_tokens`	No	Estimated tokens injected from prior experience for this task.
`evidence_count`	No	Number of relevant prior experiences supporting the decision.
`policy_version`	No	OpenReflex decision-policy version used for the score.
`route_advantage`	No	Normalised advantage of the recommended route over the next best route.
`next_best_strategy`	No	Highest-ranked alternative strategy, if any.
`decision_confidence`	No	Confidence in the recommendation from the available evidence.
`success_probability`	No	Estimated probability of success for the recommended strategy.

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedv0.5.1Sep 19, 2026

addedOutput schema / properties / available

Added value: +{
+  "description": "Whether a decision snapshot is available for the most recent decided task.",
+  "title": "Available",
+  "type": "boolean"
+}

addedOutput schema / properties / budget_used

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Largest fraction of the task budget consumed across time, calls and context.",
+  "title": "Budget Used"
+}

addedOutput schema / properties / context_tokens

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Estimated tokens injected from prior experience for this task.",
+  "title": "Context Tokens"
+}

addedOutput schema / properties / decision_confidence

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Confidence in the recommendation from the available evidence.",
+  "title": "Decision Confidence"
+}

addedOutput schema / properties / evidence_count

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Number of relevant prior experiences supporting the decision.",
+  "title": "Evidence Count"
+}

addedOutput schema / properties / next_best_strategy

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Highest-ranked alternative strategy, if any.",
+  "title": "Next Best Strategy"
+}

addedOutput schema / properties / policy_version

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "OpenReflex decision-policy version used for the score.",
+  "title": "Policy Version"
+}

addedOutput schema / properties / reason

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Why no score is available, when available is false.",
+  "title": "Reason"
+}

addedOutput schema / properties / reflex_score

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Strength of the recommendation on a 0-100 scale; not success probability.",
+  "title": "Reflex Score"
+}

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

addedOutput schema / properties / route_advantage

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Normalised advantage of the recommended route over the next best route.",
+  "title": "Route Advantage"
+}

addedOutput schema / properties / signals

Added value: +{
+  "additionalProperties": {
+    "type": "number"
+  },
+  "description": "Normalised component signals used to compute the Reflex Score.",
+  "title": "Signals",
+  "type": "object"
+}

addedOutput schema / properties / strategy

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Recommended strategy for the latest decision.",
+  "title": "Strategy"
+}

addedOutput schema / properties / success_probability

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Estimated probability of success for the recommended strategy.",
+  "title": "Success Probability"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "available"
+]

changedOutput schema / title

Previous value: -"get_reflex_scoreOutput"New value: +"ReflexScoreResult"

Addedv0.3.2Sep 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, and the description adds value by stating side effects are none, errors occur until project approval, and availability behavior when no decision exists. It also clarifies that the Reflex Score is recommendation strength, not success probability.

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 organized into purpose, return contents, usage guidance, exclusions, side effects, and errors. Each section earns its place, and the core purpose is front-loaded before the detailed field list.

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?

With zero parameters and an output schema present, the description still covers availability, error behavior, side effects, and sibling-tool distinctions. Nothing needed to invoke or interpret the tool is missing.

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 there is no parameter burden for the description to carry. The description instead clarifies the output contract, which is the relevant semantic content for this tool.

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?

Clearly states the verb 'Return', the resource 'latest decision's Reflex Score', and the machine-readable component fields. It explicitly distinguishes itself from explain_decision and get_execution_trace, so an agent can identify its unique purpose without inspecting siblings.

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?

Provides explicit 'Use when' guidance for programmatic inspection of decision numbers, and 'Not for' guidance with named alternatives for prose explanations and full timelines. This leaves no ambiguity about when to select this tool.

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

Deploy Server