Skip to main content
Glama
Sign In
telegraph-mcp

telegraph-mcp

Official
by telegraphprotocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Miner ranking

telegraph_ranking
Read-only

Get the current epoch's miner rankings by intent, with scores from the network's own checks. Use it to pick the top live miner to send an ask to.

Instructions

The latest epoch's miner ranking (scores from the network's own checks), for one intent or the top few of every intent. Asks go to the top live miner. Free.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMiners per intent (default 10 for one intent, 3 for all).
intentNoIntent name. Empty: every ranked intent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real context beyond them: the data is scoped to "the latest epoch," the scores come from "the network's own checks," and the call is "Free" (no cost/quota concern). It does not describe the response shape or whether ranking data can be stale within an epoch, which keeps it short of a 5.

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?

Two short sentences, all content front-loaded: what the data is and its provenance first, then retrieval scope, then the practical note about asks and cost. No sentence is 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 simple two-parameter read tool with no output schema, the description covers freshness, data source, scope, and cost. The remaining gap is that it does not hint at what a ranking entry contains or how ties/missing intents are handled, but nothing needed to invoke it correctly is missing.

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% and the schema already documents the per-intent defaults (10 for one intent, 3 for all). The description's "for one intent or the top few of every intent" reinforces that split but adds no format or edge-case detail beyond what the schema states, so baseline 3 applies.

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 latest epoch's miner ranking ... for one intent or the top few of every intent" names a specific resource (miner ranking), its freshness, and the two modes of retrieval. It is clearly distinguishable from siblings like telegraph_find_miners or telegraph_intent, though it never names a sibling explicitly.

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?

"Asks go to the top live miner" plus "Free." implies the ranking is consulted to decide who to ask and that reading it carries no cost. However, there is no explicit when-to-use/when-not guidance and no comparison against telegraph_find_miners, so the agent must infer the selection context.

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

Deploy Server

Other Tools