Skip to main content
Glama

flop_alert_subscribe

Create an alert that fires when a miner's settle_rate drops below threshold. Returns alert_id. Use address "*" to watch every miner at once. channel="site" requires polling with flop_alert_check to detect firing; channel="telegram" pushes a message to handle when the threshold is crossed. threshold is a fraction 0–1 (e.g. 0.5 fires when settle_rate drops below 50%).

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": {
      "threshold": "<threshold>"
    },
    "name": "flop_alert_subscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNoTelegram chat id or @username; required for telegram channel
addressNoSS58 miner address, or "*" for all miners
channelNo"site" = poll flop_alert_check to detect firing; "telegram" = push to handle
thresholdYesFraction 0–1; alert fires when settle_rate drops below this value

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"SS58 address, or \"*\" for every miner"New value: +"SS58 miner address, or \"*\" for all miners"
    • addedInput schema / properties / channel / description
      Added value: +"\"site\" = poll flop_alert_check to detect firing; \"telegram\" = push to handle"
    • changedInput schema / properties / handle / description
      Previous value: -"Telegram chat id or @username; empty for site"New value: +"Telegram chat id or @username; required for telegram channel"
    • addedInput schema / properties / threshold / description
      Added value: +"Fraction 0–1; alert fires when settle_rate drops below this value"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, non-destructive mutation, and the description usefully adds the delivery mechanics for each channel and the fact that an alert_id comes back. It does not address whether calling twice creates two independent alerts, which matters given idempotentHint=false, nor any auth requirements.

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?

Four sentences, each doing distinct work: purpose, return value, wildcard addressing, channel behavior, threshold units. The trigger condition and return value are front-loaded with no filler.

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 four-parameter creation tool with 100% schema coverage and no output schema, the description covers trigger semantics, return value, and both channel workflows. Lifecycle questions (how to remove or list existing alerts) are the only meaningful gap.

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 coverage is 100%, so the schema already documents all four parameters including the "*" wildcard and the 0–1 threshold range. The description mostly restates those semantics, adding only the concrete 0.5 = 50% example as genuine extra clarity, so the baseline 3 is appropriate.

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?

The first sentence gives a specific verb ('Create an alert'), the exact trigger condition ('miner's settle_rate drops below threshold'), and the return value ('alert_id'). It is immediately distinguishable from flop_alert_check, which the description itself frames as the polling counterpart.

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?

It states clearly how to select each mode: channel="site" means you must poll with flop_alert_check, channel="telegram" pushes to the given handle, and address="*" watches all miners. What's missing is any exclusion guidance, such as whether an agent should prefer one channel by default or how repeated subscriptions relate to each other.

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.