Skip to main content
Glama

flop_miner_ranking

Read-onlyIdempotent

Return FLOP inference miners ranked by reliability. Each entry includes address, settle_rate (fraction of on-chain tasks settled, 0–1), local_success (Scout's own observed success rate), avg_latency_ms, and score. Higher score is better. Use to pick a reliable miner, monitor network health, or feed into an alert subscription.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 adds valuable semantics the annotations cannot: the exact return fields, the 0–1 range of settle_rate, the fact that local_success is Scout's own observation rather than on-chain data, and that higher score is better. It does not disclose how many miners are returned, ranking staleness, or tie-breaking, which are the notable remaining gaps.

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 sentences, front-loaded with what is returned before the field breakdown and use cases. Every sentence earns its place, and the field list is necessary because no output schema exists to carry it.

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 must document the response, and it does name and explain all five fields. It stops short of stating result count, refresh cadence, or score scale bounds, minor but real omissions for a monitoring/alerting input.

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 no parameter meaning to add and the baseline of 4 applies. The enumerated fields describe the response payload rather than inputs and are better credited under behavioral transparency.

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 ('Return') and resource ('FLOP inference miners'), plus the ranking criterion ('ranked by reliability'). The 'ranked by reliability' framing distinguishes it from the sibling flop_miner_history, which by name alone implies historical records rather than a current ranking, without needing to open 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 Guidelines4/5

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

Gives three concrete use cases: picking a reliable miner, monitoring network health, and feeding an alert subscription. It does not state when-not to use it or explicitly name an alternative (e.g., history vs. current snapshot), so it sits at a clear 4 rather than a 5.

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.