Skip to main content
Glama

flop_miner_history

Read-onlyIdempotent

Return the settle_rate time series for one miner from Scout's 15-minute snapshots. Each point has ts (Unix timestamp) and settle_rate (0–1). A short response span means the miner was recently added, not that it is stable. Use window to zoom in on a recent period, or points to control resolution. Useful for trend analysis and alerting context.

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": {
      "address": "<address>"
    },
    "name": "flop_miner_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsNo
windowNoseconds, default 604800 (7 days)
addressYesSS58 miner address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description does add genuinely useful context beyond that: 15-minute snapshot granularity, the value range (0–1), and the important caveat that a short response span signals a recently added miner rather than instability. It says nothing about ordering, truncation at the 500-point cap, or error behavior, so it is good but not rich.

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?

Four short sentences, front-loaded with the return shape and followed by the interpretation caveat and tuning hints; nothing is buried or repeated. The closing 'useful for trend analysis and alerting context' is the only sentence that borders on 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?

With no output schema, the description correctly takes on the job of describing the return payload (ts plus settle_rate per point) and its granularity, and it flags the main interpretation pitfall. Missing only secondary details such as point ordering and how the 500-point maximum interacts with window.

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 67%, with `points` carrying no schema description at all; the description partially compensates by explaining that points controls resolution and window zooms to a recent period. It does not explain the interaction between the two (e.g., that window plus the 15-minute cadence determines the point count) or what happens when points exceeds the available data, so the added meaning is modest.

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?

The description opens with a specific verb and resource: 'Return the settle_rate time series for one miner,' and names the underlying data source (Scout's 15-minute snapshots). That is enough to separate it from siblings like flop_miner_ranking (a ranking) or flop_alert_check (an alert lookup), though it never explicitly contrasts with them.

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

Usage Guidelines3/5

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

'Useful for trend analysis and alerting context' plus the window/points tuning tips imply when the tool fits, but there is no explicit when-to-use-versus-alternative guidance or exclusion (e.g., when to prefer the ranking tool). The agent must infer the boundary from the sibling names.

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.