Cipher — Bittensor Subnet Screener

subnet_detail

Full detail for one subnet: price, 1d/1w/1m change, volume, liquidity, identity tags, research conviction, watchlist.

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": {
      "netuid": "<netuid>"
    },
    "name": "subnet_detail"
  }
}

Input Schema

Name	Required	Description	Default
`netuid`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet the read-only nature is only implied by the noun phrase "Full detail." It says nothing about behavior for an unknown netuid, auth requirements, or response framing. The field enumeration leans on data that the output schema already covers rather than disclosing new behavior.

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?

One front-loaded sentence with a comma-separated field list and no filler. Slight inefficiency in that the enumerated fields restate what the existing output schema already declares.

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 one-parameter lookup with an output schema, the definition supplies what is actually needed to call it correctly: the resource, the required identifier, and the shape of the return. The remaining gap, explaining netuid and its provenance, is real but modest for a simple read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter netuid has 0% schema description coverage, so the description was the place to explain it, and it does not mention the parameter at all. An agent must assume netuid is the numeric subnet identifier, which is domain knowledge the definition never supplies or confirms.

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 resource and scope ("Full detail for one subnet") and enumerates exactly what is returned: price, 1d/1w/1m change, volume, liquidity, identity tags, research conviction, watchlist. That is enough to tell it apart from a time-series tool like subnet_bars, but the description never names or contrasts any sibling, so differentiation is left partly to inference.

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?

Usage is only implied by the field list: this is the tool for inspecting a single subnet's full profile. There is no explicit when-to-use statement, no guidance on picking it over subnet_bars or search_subnets, and no prerequisites or exclusions. Adequate to guess, not adequate to be sure.

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?