Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_scheduler_list_triggers

Lists all research triggers with their IDs so you can identify and reference scheduled triggers when managing automated research tasks.

Instructions

List research triggers and their IDs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden, and 'List' only weakly implies a read-only operation. It says nothing about whether results are paginated, sorted, scoped to a workspace or research run, or what happens when no triggers exist.

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 short sentence, front-loaded with the verb and resource, with no filler. It is terse but proportionate to a zero-argument listing tool.

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?

The tool itself is simple, but there is no output schema, so the description is the only place an agent could learn the shape of the response; 'their IDs' gestures at it without describing fields or ordering. Enough to call correctly, not enough to interpret results confidently.

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

Parameters4/5

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

The input schema declares zero parameters, so there is no per-parameter meaning to add; baseline for a parameterless tool is 4. The description correctly implies the call takes no arguments.

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?

States a specific verb and resource ('List research triggers') plus what is returned ('their IDs'), which separates it from mutation siblings like reflex_scheduler_add_trigger or remove_trigger. It does not, however, contrast itself with reflex_scheduler_list_tasks, which lists a different object type in the same scheduler family.

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 prerequisite or scoping statement, and no pointer to alternatives such as reflex_scheduler_check_coverage or reflex_scheduler_stats, which an agent might plausibly confuse with a listing tool. Usage is only implied by the verb 'List'.

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