Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_scheduler_remove_trigger

Removes a research trigger by its ID, deleting a scheduled trigger from the scheduler so it no longer fires.

Instructions

Remove a research trigger by ID.

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": {
      "trigger_id": "<trigger_id>"
    },
    "name": "reflex_scheduler_remove_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
trigger_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/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 for a destructive operation. It does not state that removal is permanent, whether an active trigger fires mid-removal, whether permission or ownership is required, or what happens when the ID does not exist.

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 wasted words, which is good structure, but the brevity reflects under-specification rather than disciplined concision. Nothing is front-loaded beyond the bare action.

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 unannotated destructive tool with no output schema and an undocumented parameter, the description should explain permanence, failure behavior, and ID provenance. None of these are covered, leaving the definition inadequate relative to its risk profile.

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 description coverage is 0%, so the only parameter guidance comes from 'by ID'. The description does not say the expected ID format or that IDs can be obtained from reflex_scheduler_list_triggers, which is the key missing semantic for a lookup-based deletion.

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 sentence gives a specific verb ('Remove') and resource ('research trigger') scoped by identifier, which is enough to separate it from reflex_scheduler_add_trigger and the task-oriented siblings. It stops short of explicitly contrasting with reflex_scheduler_remove_task, but the trigger/resource distinction is clear.

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 remove a trigger versus disabling it or removing a task, no prerequisites, and no mention of what to do if the ID is unknown. The agent is left to infer the entire usage context from the name and one sentence.

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