Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_list_lessons

Lists lessons from the continual learning brain, with optional filters by status and cluster to retrieve relevant knowledge.

Instructions

List lessons with optional filters

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reflex_list_lessons"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNoFilter by status: proposed, accepted, deprecated, superseded
cluster_idNoFilter by cluster

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/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 disclosure burden, yet it says nothing about read-only semantics, ordering, pagination, or permissions. Only the default limit and max are visible in the schema; the description adds no behavioral context at all.

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 five-word sentence with zero filler, and the core purpose is front-loaded. Its brevity is efficient rather than padded, though it borders on under-specification.

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

Completeness2/5

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

With three parameters, no annotations, no output schema, and many list/get siblings, this definition should explain what a lesson is, how results are ordered or paged, and how to narrow them. None of that is present, leaving the agent to guess at return shape and filter behavior.

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

Parameters2/5

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

Schema coverage is 67%: status and cluster_id are documented in the schema, but limit has no description beyond default/min/max bounds. The description says only "optional filters" and does not clarify which filters exist, what values are valid, or what limit controls.

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?

The description gives a clear verb ("List") and resource ("lessons") and notes that filters are optional, so an agent can tell it returns lesson collections rather than single records. It does not distinguish itself from siblings like reflex_list_proposals or reflex_list_skills, and it never contrasts with reflex_get_lesson.

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?

"with optional filters" hints that filtering is available but gives no when-to-use context, no prerequisites, no exclusions, and no pointer to alternatives such as reflex_query or reflex_get_lesson. The agent must infer the use case entirely from the tool name.

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