Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_scheduler_remove_task

Remove a scheduled research task by task ID to cancel its future execution in the reflex-brain scheduler.

Instructions

Remove 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": {
      "task_id": "<task_id>"
    },
    "name": "reflex_scheduler_remove_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesTask ID to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/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 does not meet it. It doesn't say whether removal is permanent, whether in-flight or scheduled runs are cancelled, whether an unknown task_id errors or silently succeeds, or whether permissions are required — all critical for a destructive operation.

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 that is front-loaded and free of waste. It is under-specified rather than verbose, so length is not the problem.

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 a destructive, unannotated, single-parameter tool with no output schema, the description omits irreversibility, failure behavior, and ID provenance. Those gaps matter more than any return-value detail here.

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?

Only one parameter exists and the schema documents it fully at 100% coverage, so the baseline of 3 applies. The description adds nothing beyond the schema, such as where task IDs come from or whether they are the same identifiers used by add_task.

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?

"Remove a scheduled research task" names a specific verb and resource, and the word "task" distinguishes it from the sibling remove_trigger. It is clear enough to select without opening the schema, though it doesn't state why a caller would remove a task instead of pausing or disabling it.

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?

No when-to-use or when-not-to-use guidance is given, and no prerequisites are stated. It never points the agent to list_tasks to obtain a valid task_id, nor distinguishes removal from remove_trigger, leaving the agent to infer both from the name alone.

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