SiteCheck Crypto & Finance

Bittensor EVM activity monitor: recent blocks, transaction

crypto_subtensor_evm_activity

Read-only

Bittensor EVM (Chain ID 964) activity monitor: recent blocks, transaction counts, gas used/limit, gas utilization %, and top smart contracts called across the window (1-20 blocks). Related tools on this server, for a different need: crypto_subtensor_weights_activity when you need recent validator weight-setting extrinsics on Subtensor; crypto_subtensor_block_events when you need events of a single Bittensor Subtensor block by block. 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_evm_activity"
  }
}

Input Schema

Name	Required	Description	Default
`blocks`	No	Number of recent EVM blocks to analyze (1-20, default 5)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely new operational context: a 1-20 block analysis window, a $0.005 per-successful-call x402 price across Base/Solana/Arc, and the guarantee that failed calls are not charged. It does not add further detail on latency or result shape, though an output schema exists to cover returns.

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?

Purpose is front-loaded and the metric list is compact; the related-tools and pricing sentences each carry information an agent needs before calling a paid tool. The chain-ID parenthetical and the three-payment-rail list are slightly heavy for the space they occupy.

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

Completeness5/5

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

For a single-parameter, read-only analytics tool with an output schema and annotations, the description covers what is measured, the analysis window, sibling disambiguation, and the payment model. Nothing material an agent needs to select and invoke it correctly is absent.

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?

Only one parameter exists and the schema documents it at 100% coverage including the 1-20 range and default of 5. The description restates the same window ('1-20 blocks') without adding format or behavior detail beyond the schema, so the baseline 3 applies.

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 states a specific resource and scope (Bittensor EVM, Chain ID 964) and enumerates exactly what the tool reports: recent blocks, transaction counts, gas used/limit, gas utilization %, and top contracts called. The sibling names it contrasts against (weights_activity, block_events) make clear this is the EVM-layer activity tool, not a Subtensor extrinsics/events tool.

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 routes two adjacent needs elsewhere with conditions: weights_activity 'when you need recent validator weight-setting extrinsics' and block_events 'when you need events of a single Bittensor Subtensor block'. When-to-use for this tool itself is only implied by the metric list, and no explicit exclusion for other block-range or gas tools is given.

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?