Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_scheduler_list_tasks

List scheduled research tasks and optionally filter to enabled-only entries, helping AI agents review upcoming learning work and manage scheduling.

Instructions

List scheduled research tasks

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_scheduler_list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabled_onlyNo

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?

With no annotations, "List" only implies a non-mutating read operation. The description adds no behavioral context about whether disabled tasks are included by default, result ordering or pagination, or what information is returned.

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 four-word description is front-loaded, direct, and contains no wasted wording. Its brevity is clean, although it comes at the cost of useful operational detail.

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 simple list operation with one optional Boolean parameter, the description is minimally sufficient for basic tool selection and a no-argument invocation. However, the absence of annotations and an output schema makes the unexplained filtering behavior and unspecified results more consequential.

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

Parameters1/5

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

Schema description coverage is 0%, and the description never mentions the sole enabled_only parameter. It therefore does not compensate for the schema gap or clarify the practical effect of the default value false.

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 clearly pairs the verb "List" with the resource "scheduled research tasks," making the basic operation easy to understand. It does not explicitly distinguish this tool from siblings such as reflex_scheduler_list_triggers, so it falls short of the highest score.

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?

An agent can infer that the tool is for inspecting scheduled research tasks, but the description provides no actual when-to-use guidance. It does not explain when to filter by enabled status or when a sibling listing or statistics tool would be more appropriate.

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