Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_scheduler_stats

Retrieve scheduler statistics to monitor job timing, status, and performance, helping diagnose scheduling issues and verify execution health.

Instructions

Get scheduler statistics

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/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, and it discloses almost nothing. "Get" implies a read-only operation, but there is no statement about whether the scheduler must be enabled/running, whether stats are per-workspace or global, whether they are live or cached, or how expensive the call is. For a zero-annotation tool this is a significant gap.

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 with no filler and the resource front-loaded. It is not padded, though the terseness is the source of the other gaps rather than a strength in itself.

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?

There is no output schema, so the description is the only place a caller could learn what the statistics contain, and it says nothing about the returned fields or shape. Combined with the absence of annotations and any usage context, an agent can identify the call but cannot anticipate or interpret its result.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The empty schema with additionalProperties: false is self-explanatory.

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?

States a verb ("Get") and a resource ("scheduler statistics"), which is enough to know it returns metrics rather than mutating the scheduler. However, "statistics" is left undefined — queue depth, trigger counts, next-run times, error rates are all plausible — so an agent cannot tell precisely what it gets back. It is adequately distinct from the add/remove/list siblings but vaguer than any of them.

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 and no mention of alternatives such as reflex_scheduler_list_tasks or reflex_scheduler_check_coverage, which plausibly overlap in diagnostic intent. The agent must infer that this is the tool for a health/overview check rather than a task listing.

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