Cipher — Bittensor Subnet Screener

screener_top

Top subnets by Cipher heat score. n up to 50. category filters by tag (e.g. 'inference', 'training', 'agents', 'finance', 'tools').

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

Input Schema

Name	Required	Description	Default
`n`	No
`category`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are supplied, so the description bears the full behavioral burden. It does disclose the ordering semantics ('by Cipher heat score') and the hard cap of n up to 50, but says nothing about how the score is computed, over what time window, or how fresh the data is.

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?

Three short fragments, ranking criterion front-loaded, no filler. The staccato phrasing ('n up to 50.') reads slightly like schema shorthand rather than prose, but nothing is wasted.

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

Completeness3/5

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

For a two-optional-parameter list tool with an output schema, this is close to sufficient: it establishes ordering, the size cap, and the filter vocabulary. It still leaves the meaning of 'Cipher heat score' and the behavior of a null category unspecified.

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 0%, so the description must carry the parameters — and it does add real value: the 'up to 50' upper bound on n and the tag-based meaning of category with five example values are nowhere in the schema. However, it omits the default n of 10 and doesn't state whether category matching is exact or substring.

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?

States a specific verb-and-resource outcome: a ranked list of subnet entities ordered by 'Cipher heat score'. That ranking focus implicitly separates it from lookups like search_subnets or subnet_bars, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use, when-not-to-use, or alternative routing guidance. The agent must infer from the name and the word 'Top' that this is a ranked leaderboard rather than a filtered search, with nothing steering it away from search_subnets or subnet_bars.

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

All Cipher — Bittensor Subnet Screener tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?