Skip to main content
Glama

flop_alert_check

Read-onlyIdempotent

Return active alerts and their current state. Each item has alert_id, address, threshold (the configured trigger level), settle_rate (current observed rate), and fired (true when settle_rate is below threshold). Poll this after flop_alert_subscribe with channel="site" to detect firings. Use alert_id from the response to cancel an alert via the REST API.

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": "flop_alert_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoSS58 miner address to filter results; omit to return all alerts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / address / description
      Previous value: -"filter to one miner; default all"New value: +"SS58 miner address to filter results; omit to return all alerts"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, and the description goes beyond them by defining the response items and the meaning of 'fired' (settle_rate below threshold). It also discloses an important operational fact — that cancel is not available as an MCP tool and must go through the REST API — but says nothing about polling cost, rate limits, or result ordering.

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 tight sentences, front-loaded with purpose and return shape, then usage sequencing, then the cancellation pointer. No redundant or filler wording.

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

Completeness5/5

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

With no output schema, the description takes on the burden of explaining return values and does so field by field, including the derived 'fired' flag. For a read-only, single-optional-parameter tool this covers everything needed to call and interpret it correctly.

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?

There is one optional parameter with 100% schema coverage, including the 'omit to return all alerts' semantics, so the schema already carries the meaning. The description adds nothing about the address parameter beyond noting that address appears in the response items.

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 ('Return active alerts and their current state') and enumerates the returned fields, so the agent knows exactly what it gets. It is clearly distinguishable from the sibling flop_alert_subscribe, which it explicitly references as the upstream action.

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

Usage Guidelines4/5

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

Gives explicit sequencing guidance: poll this after flop_alert_subscribe with channel="site" to detect firings, and directs cancellation to the REST API using alert_id. It does not state when-not to use it (e.g., whether polling frequency is limited or whether a non-subscribed user gets an empty list), so it stops short of full when/when-not coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.