Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_scheduler_add_trigger

Adds a low-coverage trigger that schedules automatic research when topic coverage or result thresholds are not met.

Instructions

Add a low-coverage trigger for automatic research

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_pattern": "<topic_pattern>"
    },
    "name": "reflex_scheduler_add_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTrigger name
enabledNo
topic_patternYesTopic pattern (e.g., 'DIAN*', 'agente*')
cooldown_hoursNoCooldown between triggers
min_results_thresholdNoMinimum results threshold
min_coverage_thresholdNoMinimum coverage score (0-1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.5/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 entire burden, yet it says nothing about side effects. It does not state that this creates a persistent scheduler entry that will autonomously fire research jobs, whether it fires immediately or only on cooldown, whether it conflicts with existing triggers, or what permissions/resources the automatic research consumes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, which is structurally clean and front-loaded. But the brevity is under-specification rather than economy: the one phrase used ("low-coverage") is the least self-explanatory part and is never unpacked.

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?

This is a mutation tool with six parameters, no annotations, and no output schema, so the description is the only source of behavioral context — and it supplies almost none. An agent cannot learn from it what a trigger does after creation, how it interacts with tasks, or what is returned, which is inadequate for this complexity.

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 description coverage is 83%, so parameters such as name, topic_pattern, cooldown_hours, and min_coverage_threshold are already documented with examples and defaults. The description only obliquely gestures at min_coverage_threshold via "low-coverage" and adds no format or interaction semantics beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Add ... trigger") and ties it to "automatic research", so the general action is inferable. However, the modifier "low-coverage" is unexplained jargon and nothing distinguishes this from the sibling reflex_scheduler_add_task, so the agent cannot be fully confident which creation tool it needs.

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 guidance, no statement of prerequisites (e.g., a scheduler must be running or a task must exist first), and no exclusions or alternatives named. The agent must guess whether this is the right tool versus reflex_scheduler_add_task or reflex_scheduler_check_coverage.

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