Skip to main content
Glama

xflux_get_monitor_hits

List recent hits for one XFlux monitor to retrieve read-only alert history for a watched @account. Use after listing monitors to inspect recent events by monitor_id.

Instructions

List recent hits for one XFlux monitor (read-only). Use after xflux_list_monitors when the user wants alert history for a watched @account. Create/edit monitors in the Dashboard.

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": {
      "monitor_id": "<monitor_id>"
    },
    "name": "xflux_get_monitor_hits"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax hits (default 20)
monitor_idYesMonitor id from xflux_list_monitors

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden; it does disclose that the call is read-only and depends on a monitor_id obtained elsewhere, which is useful. However it says nothing about result ordering (recency?), pagination/truncation behavior for large hit volumes, or auth requirements, which are real gaps for a history-listing tool.

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

Conciseness5/5

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

Three short sentences, front-loaded with the core action, then prerequisite, then the out-of-scope pointer. No filler or repetition of schema content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with full schema coverage and no output schema, the definition covers purpose, prerequisite, and scope adequately. It stops short of describing what a 'hit' record contains or how results are ordered, which would fully close the loop.

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 100% – both monitor_id (with its provenance note) and limit (with default 20 and 1-100 range) are fully documented in the schema. The description adds no syntax, default, or format detail beyond that, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource with scope: 'List recent hits for one XFlux monitor.' The parenthetical '(read-only)' and the reference to 'one monitor' distinguish it from the sibling xflux_list_monitors, so an agent can tell them apart without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly gives the ordering prerequisite ('Use after xflux_list_monitors'), the triggering intent ('when the user wants alert history for a watched @account'), and routes the excluded operations (create/edit) to the Dashboard. When-to-use, prerequisite, and alternative are all covered.

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