Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_scheduler_check_coverage

Checks whether a topic has sufficient knowledge coverage in the learning brain, helping agents identify gaps before planning or retrieval.

Instructions

Check knowledge coverage for a topic

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": {
      "topic": "<topic>"
    },
    "name": "reflex_scheduler_check_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesTopic to check

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 provided, so the description carries the full behavioral burden and largely fails it. 'Check' implies a read, but read-only safety is not declared, nor is whether the check is scoped to a workspace or collection, how expensive it is, or what form the result takes. For a tool with zero annotation coverage, this is a substantial gap.

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?

The definition is one short, front-loaded sentence with no filler. It is efficient, though its brevity is closer to under-specification than to disciplined concision; a clause defining 'coverage' would have earned its place.

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?

There is no output schema and no annotations, so the description must define what a coverage report contains, but it does not. The central concept, 'knowledge coverage', is left undefined, and there is no indication of scope, thresholds, or how to interpret a result. Too little is supplied for an agent to use the tool confidently.

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?

There is a single parameter, 'topic', and schema description coverage is 100%, so the schema already documents it. The description adds only the notion of coverage being 'for a topic' and no format, length, or matching semantics. Baseline 3 applies when the schema does the documentation work.

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 states a specific verb and resource: 'Check knowledge coverage' for a topic. This is distinguishable from the scheduler task/trigger management siblings and from reflex_query. It does not explicitly name an alternative, so it falls short of a 5.

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 guidance on when to use this tool versus reflex_query, reflex_status, or reflex_get_skill. No prerequisites, no exclusions, and no statement of what 'coverage' means in practice. The agent must infer all usage context from the name alone.

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