Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_scheduler_add_task

Schedule recurring research tasks with a topic, frequency, and source limit to automate ongoing AI research and retain findings.

Instructions

Add a scheduled research task

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

Input Schema

NameRequiredDescriptionDefault
nameYesTask name
topicYesResearch topic
enabledNo
frequencyNoSchedule frequencydaily
max_sourcesNoMaximum sources per run
create_lessonsNo
create_memoriesNo
cron_expressionNoCustom cron expression (if frequency=custom)

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 supplied, the description carries the full behavioral burden and discloses almost nothing. It does not say whether the task starts firing immediately, whether it is persisted across sessions, what permissions or config it needs, or what happens to the flags like create_lessons and create_memories; only the bare 'add' mutation is implied.

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 single short phrase is front-loaded and free of filler, so nothing is wasted. Its brevity is efficient rather than padded, though it borders on under-specification rather than tightness.

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?

For an eight-parameter creation tool with no annotations and no output schema, this is far too thin: the agent gets no notion of side effects, defaults behavior, or the scheduler's lifecycle. Only the core intent is communicated.

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 63%, leaving enabled, create_lessons, and create_memories undocumented in structured fields, and the description adds no meaning for any of the eight parameters. It also does not clarify the custom-frequency/cron_expression interaction, which is the one place a sentence would have real value.

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 specific verb and resource ('Add a scheduled research task'), which is meaningfully more informative than the bare tool name and distinguishes it from the sibling trigger tools and from remove/list variants. It stops short of explicitly contrasting with reflex_scheduler_add_trigger, but the task-vs-trigger noun does most of that work.

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 create a task versus adding a trigger, nor any prerequisites such as whether the scheduler must already be running or whether the task runs immediately on creation. The agent must infer usage entirely from the name and sibling list.

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