Skip to main content
Glama
Sign In
Carbon Cashmere MCP Server

Carbon Cashmere MCP Server

Official
by CarbonCashmere
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_v1_bittensor_derivatives_subnet_netuid_stake_flows

View per-neuron stake accumulation, distribution, net flow, and concentration trends for a Bittensor subnet using high-cadence snapshots.

Instructions

dTAO stake-flow microstructure per subnet: per-neuron accumulation/distribution, net flow, concentration trend from months of continuous high-cadence snapshots. Informational research data — not investment advice. Price: $0.10. Category: bittensor-mantis.

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

Input Schema

NameRequiredDescriptionDefault
netuidYesPath parameter netuid (e.g. BTC, ETH, SOL, or other supported identifier)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions 'from months of continuous high-cadence snapshots', indicating historical data, but does not disclose data freshness, real-time vs static nature, or any side effects. The price and category are given but do not address behavioral concerns. Lacks clarity on potential issues like rate limits or output size.

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?

The description is extremely concise: one sentence conveying purpose, followed by a disclaimer and metadata. Every part is necessary and front-loaded. No fluff or redundancy.

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 single-parameter tool with no output schema, the description explains the core metrics (accumulation/distribution, net flow, concentration trend) and temporal scope (months of snapshots). It lacks details on output format or interpretation, but given the straightforward input, it is fairly complete. The price and category add mild context.

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% for the only parameter (netuid), which is well-described in the schema as a path parameter with examples. The description reinforces 'per subnet' but adds no new semantic information beyond the schema. Thus baseline 3 is appropriate.

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?

The description clearly states what the tool does: 'dTAO stake-flow microstructure per subnet: per-neuron accumulation/distribution, net flow, concentration trend'. It specifies the resource (subnet identified by netuid) and the type of data (stake flows). This differentiates it from sibling tools like get_v1_bittensor_derivatives_subnet_netuid (general subnet info) and get_v1_bittensor_derivatives_alpha_prices (alpha prices).

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?

The description implies usage for stake-flow analysis but does not explicitly state when to use it versus alternatives. There is no mention of when not to use it or which other tools to consider. The disclaimer 'Informational research data — not investment advice' provides context but no comparison to siblings.

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