Skip to main content
Glama
vishnu-77

OpenReflex

by vishnu-77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Choose path

choose_path
Idempotent

Record the strategy you actually follow when departing from the suggested path, so the local Experience Graph logs the real approach instead of the recommendation.

Instructions

Declare the strategy you are following for the most recent task. Returns: one line, 'Recorded chosen path: '. Use when: deliberately departing from the suggested path, so OpenReflex remembers what was actually done rather than confusing the recommendation with the observed work. Not for: tasks that follow the suggestion; the path is then inferred from tool activity. Side effects: writes the choice to the local Experience Graph; calling it again replaces the earlier choice. Touches no project files. Errors: 'No current execution' before any task was planned (call get_execution_context first); a 'not enabled' message until the project is approved.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stepsNoFor a custom strategy only: 2-4 short steps, e.g. ['Prototype the toml loader', 'Swap the callers']. Ignored for suggested strategies.
strategyYesThe strategy being followed: one of the suggested names 'inspect-first', 'test-first' or 'incremental', or a short kebab-case name for your own, e.g. 'spike-then-rewrite'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.1
    • addedInput schema / properties / strategy / maxLength
      Added value: +60
    • addedInput schema / properties / strategy / minLength
      Added value: +1
  2. Changed2 schema fields changedv0.3.2
    • addedInput schema / properties / steps / description
      Added value: +"For a custom strategy only: 2-4 short steps, e.g. ['Prototype the toml loader', 'Swap the callers']. Ignored for suggested strategies."
    • addedInput schema / properties / strategy / description
      Added value: +"The strategy being followed: one of the suggested names 'inspect-first', 'test-first' or 'incremental', or a short kebab-case name for your own, e.g. 'spike-then-rewrite'."
  3. First observedv0.1.3

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the tool writes to the local Experience Graph, replaces earlier choices on repeated calls, and touches no project files. It also lists two specific error conditions, giving the agent a clear behavioral model. The idempotentHint annotation is consistent with replacing an earlier choice with the same choice.

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 labeled segments — Returns, Use when, Not for, Side effects, Errors — that are easy to scan. Every sentence carries operational value, and the core purpose is front-loaded before details.

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?

The description covers when to use the tool, what it returns, side effects, prerequisites, and failure modes. Given the rich schema and output schema, nothing essential is missing for an agent to select and invoke this tool correctly.

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?

Schema coverage is 100%, with both strategy and steps already explained in the input schema. The description adds context about the strategy's role but no additional parameter-level meaning, so the baseline of 3 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 opens with a specific verb and resource: 'Declare the strategy you are following for the most recent task.' It clearly distinguishes the tool from siblings like record_outcome or check_progress by framing this as the act of recording a deliberately chosen path rather than observing activity.

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' guidance, stating it is for departing from the suggested path and not for tasks that follow the suggestion. It also references the prerequisite get_execution_context in the error section, giving the agent actionable routing.

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