Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_get_lesson

Retrieve a specific lesson by ID from the reflex-brain continual learning system to access stored knowledge for AI agents.

Instructions

Get a specific lesson by ID

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": {
      "lesson_id": "<lesson_id>"
    },
    "name": "reflex_get_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
lesson_idYesLesson ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about failure behavior for unknown IDs, whether the full lesson body or metadata is returned, or any read permissions. For a simple lookup this is low risk, but the disclosure gap is real.

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?

A single short sentence with zero padding and the resource front-loaded after the verb. It is efficient, though so terse that structure is essentially absent.

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

Completeness3/5

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

For a one-parameter read tool with full schema coverage and no output schema, the definition is minimally viable. It still leaves an agent unsure what the returned lesson contains and how missing IDs are handled.

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% and the single lesson_id parameter is documented in the schema, so the baseline of 3 applies. The description adds no format, origin, or example semantics for the ID beyond what the schema already states.

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?

States a specific verb (get) and resource (a specific lesson) plus the lookup key (ID), which distinguishes it from reflex_list_lessons. It does not, however, differentiate itself from near-siblings such as reflex_get_skill or reflex_get_refinement, so the agent must infer the boundary from the noun alone.

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 when-to-use, when-not-to-use, or alternative guidance at all. The only implied guidance is that a known lesson ID is required, which the agent must derive from the schema rather than the description.

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