SiteCheck Crypto & Finance

Recent TAO token transfers on Subtensor with transfer

crypto_subtensor_transfers

Read-only

Recent TAO token transfers on Subtensor with transfer volume in TAO, from/to addresses, transaction hashes, fees, and block numbers. Requires TAOSTATS_API_KEY. Related tools on this server, for a different need: crypto_subtensor_events when you need Recent Subtensor chain events, optionally filtered; crypto_subtensor_evm_activity when you need Bittensor EVM activity monitor: recent blocks, transaction. Price: $0.005 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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

Input Schema

Name	Required	Description
`page`	No	Page number
`limit`	No	Maximum transfers to return
`address`	No	Optional SS58 account address to filter transfers

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description adds two operationally important facts an agent cannot get from annotations: a TAOSTATS_API_KEY is required, and each successful call costs $0.005 USDC via x402 with failed calls not charged. That cost/auth disclosure is high-value; pagination behavior is left to the schema.

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 core purpose and return fields, followed by auth and pricing. Slightly verbose in the sibling routing sentence, but every sentence carries usable information and nothing is redundant.

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?

With an output schema present, the description does not need to enumerate return values, and it covers the remaining gaps an agent needs: authentication requirement, cost model, and sibling disambiguation. Only the multi-direction semantics of the address filter are unaddressed.

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%, so page, limit and address are already documented in the schema. The description mentions 'from/to addresses' but does not clarify whether the address filter matches sender, receiver, or both, so it adds no real meaning beyond the schema baseline.

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: recent TAO token transfers on Subtensor, with the fields returned (volume, from/to addresses, hashes, fees, block numbers). This clearly separates it from generic chain-event tools, though the phrasing 'with transfer volume in TAO' is slightly awkward and list-heavy.

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?

Explicitly routes to alternatives: crypto_subtensor_events for chain events and crypto_subtensor_evm_activity for EVM activity, each with a stated need-condition. It does not state when this tool should be avoided (e.g. for historical or non-TAO token movements), so it stops short of full when/when-not coverage.

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

All SiteCheck Crypto & Finance 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?