Skip to main content
Glama
vishnu-77

OpenReflex

by vishnu-77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get execution context

get_execution_context

Retrieve a plan from past project experience, with approach, budget, files, and lessons to guide execution.

Instructions

Plan a task from this project's past experience. Returns: plain text with the learned project Reflex procedure when one applies; otherwise a neutral working approach, relevant past experience, budget, likely files/sources and lessons. Internal strategy names and candidate scores are deliberately omitted from this normal surface; use get_candidate_paths for diagnostics. Use when: starting any substantial coding, investigation, research, analysis, review, planning or reasoning task and no [OpenReflex] block was injected. Not for: looking up history (use search_experience) or checking progress mid-task (use check_progress). Side effects: starts or re-plans the current task in the local Experience Graph; touches no project files, runs no commands, sends nothing over the network. Calling it again for the same task returns the same plan unless new limits are given. Errors: invalid non-positive limits are rejected by the input schema; a 'not enabled' message is returned until the project is approved.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesThe task in one or two plain sentences, e.g. 'Fix the login redirect loop after logout'. Used to find similar past tasks; secrets are redacted before it is stored.
max_minutesNoOptional cap on active working time in minutes; a positive number. Default: no cap.
max_tool_callsNoOptional cap on tool calls for this task; a positive integer. Default: no cap.
max_context_tokensNoOptional cap on tokens of tool output added to context; a positive integer. Default: no cap.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.1
    • changedInput schema / properties / max_context_tokens / anyOf
      Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "exclusiveMinimum": 0,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / max_minutes / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "exclusiveMinimum": 0,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / max_tool_calls / anyOf
      Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "exclusiveMinimum": 0,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / task / maxLength
      Added value: +1000
    • addedInput schema / properties / task / minLength
      Added value: +1
  2. Changed4 schema fields changedv0.3.2
    • addedInput schema / properties / max_context_tokens
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional cap on tokens of tool output added to context; a positive integer. Default: no cap.",
+  "title": "Max Context Tokens"
+}
    • addedInput schema / properties / max_minutes
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional cap on active working time in minutes; a positive number. Default: no cap.",
+  "title": "Max Minutes"
+}
    • addedInput schema / properties / max_tool_calls
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional cap on tool calls for this task; a positive integer. Default: no cap.",
+  "title": "Max Tool Calls"
+}
    • addedInput schema / properties / task / description
      Added value: +"The task in one or two plain sentences, e.g. 'Fix the login redirect loop after logout'. Used to find similar past tasks; secrets are redacted before it is stored."
  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?

Annotations only mark non-read-only/non-destructive, which is thin; the description carries the behavioral burden. It discloses that the call starts/re-plans a task in the local Experience Graph, touches no files/commands/network, is repeatable (same plan unless new limits are given), and can return a 'not enabled' message. This significantly exceeds annotation coverage.

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?

Though longer than typical tool descriptions, it is broken into labeled sections (Returns, Use when, Not for, Side effects, Errors) that each add distinct value. The core purpose is front-loaded in the first sentence, and no sentence is redundant with the schema.

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?

Covers every decision an agent needs: what it returns, when to use it, which siblings to prefer, side effects, repeat-call behavior, and error conditions. Combined with the output schema, nothing important is missing.

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 description coverage is 100% and every parameter (task, max_minutes, max_tool_calls, max_context_tokens) already has a clear schema description. The tool description adds only minor context ('unless new limits are given'), so it meets the baseline but does not meaningfully compensate beyond the schema.

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?

Description opens with a specific verb-object ('Plan a task from this project's past experience') and clarifies the return format. It explicitly distinguishes itself from sibling tools like get_candidate_paths, search_experience, and check_progress, so an agent can select it confidently.

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?

Contains an explicit 'Use when' condition (starting substantial work with no [OpenReflex] block injected) and a 'Not for' section naming alternatives (search_experience for history, check_progress for mid-task checks). This is exactly the when/when-not/alternatives guidance requested.

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