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_validators

Retrieve top-N validators ranked by incentive for a specified Bittensor subnet. Filter for validator_permit=true to support stake delegation decisions.

Instructions

Top-N validators ranked by incentive for tracked Bittensor subnets. Filter only validator_permit=true neurons. AI agent API for validator-selection and stake-delegation decisions. Informational research data — not investment advice. Price: $0.02. 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_validators"
  }
}

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

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only includes a disclaimer ('not investment advice') but does not disclose behavioral traits such as read-only nature, rate limits, caching, or response size. The tool is likely a read operation, but this is not stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences. The purpose is front-loaded, but it includes extraneous elements like price and category which are not essential for understanding the tool's function. Could be more concise.

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

Completeness2/5

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

For a tool with no output schema and no annotations, the description should explain expected output structure (e.g., list of validators with fields). It does not mention return format, ordering, or pagination, leaving the AI agent with gaps.

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 coverage is 100% (one parameter with description). The tool description adds the context of 'Top-N' and 'incentive ranking' but does not elaborate on accepted netuid values beyond the schema's examples. It meets the baseline for a well-covered schema.

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 'Top-N validators ranked by incentive for tracked Bittensor subnets' and specifies a filter ('validator_permit=true'). This distinguishes it from sibling tools like get_v1_bittensor_derivatives_subnet_netuid (general subnet data) and get_v1_bittensor_derivatives_top_validators_cross_subnet (cross-subnet).

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

Usage Guidelines4/5

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

It explicitly says 'AI agent API for validator-selection and stake-delegation decisions', providing a clear use case. However, it does not explicitly mention when not to use it or name alternatives like the cross-subnet tool, missing some exclusion guidance.

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