Cipher — Bittensor Subnet Screener

trader_state

Live AA subnet-trader decision state (read-only window): current equity + 24h trend, circuit-breaker status, open positions, and the most recent entry/exit/flow-gate decisions from the driver log. Same data as the paid x402 endpoint /api/premium/trader-stream, exposed free here for agent visibility. NEVER writes or controls the trader — a data window.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does so well on the most important axis: 'read-only window' and 'NEVER writes or controls the trader' explicitly rule out mutation, which an agent could not otherwise infer. It also discloses the data source (driver log) and equivalence to the paid endpoint. It stops short of stating refresh cadence, latency, or any rate/access constraints on the free mirror.

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?

Front-loaded with the resource and its contents, and the source note comes last where it belongs. Mild redundancy: 'read-only window', 'exposed free', and 'NEVER writes or controls the trader — a data window' restate the same non-mutation guarantee three times, which costs a little space for no added information.

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?

An output schema exists, so return values need not be explained, and the description sensibly spends its words on scope, mutability, and provenance instead. The one remaining gap is freshness: 'Live' is asserted but never quantified, which matters for a state-window tool whose whole value is currency.

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 nothing for the description to disambiguate; baseline applies. The definition correctly avoids inventing filter or time-range parameters that do not exist.

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 resource (live AA subnet-trader decision state) and enumerates its contents: equity plus 24h trend, circuit-breaker status, open positions, and recent entry/exit/flow-gate decisions. No sibling tool covers trader state, and the definition makes that scope unambiguous without opening the schema.

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 implied rather than prescribed: 'exposed free here for agent visibility' signals this is the free visibility path versus the paid /api/premium/trader-stream endpoint, which is a genuine named alternative. However, there is no explicit statement of when to call this versus the other listed tools, nor any exclusions or preconditions.

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?