Skip to main content
Glama

Explain Subtensor concepts

subtensor_explain
Read-onlyIdempotent

Understand Bittensor concepts, workflows, mechanisms, runtime APIs, runtime errors, extrinsic format, or get code examples.

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": {
      "topic": "<topic>"
    },
    "name": "subtensor_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoTopic-specific name: concept name ('staking'), workflow ID ('add-stake'), mechanism ID ('yuma-consensus'), runtime API name ('NeuronInfoRuntimeApi'), or item name for examples
topicYesWhat to explain
formatNoResponse format: 'text' (compact, default) or 'json' (structured)
palletNoPallet name — required for examples (e.g., 'SubtensorModule')
languageNoFor examples: filter to one language (overrides session preference)
node_urlNoFor examples: WebSocket endpoint override
enum_slugNoFor runtime_errors: get a specific error enum
item_typeNoFor examples: type of item to generate code for
node_typeNoFor examples: 'lite' (current state) or 'archive' (historical patterns)
preferencesNoPreferences handle from subtensor_preferences(action="set"). Carries language/node_url/node_type without a session. Explicit arguments on this call take precedence over the handle.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds no behavioral context of its own (no rate limits, no caching, no notes on how preferences handles resolve), so it neither helps nor contradicts.

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?

A single front-loaded sentence that covers the main use cases without preamble. It is slightly redundant with the topic enum but not bloated.

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 and all 10 parameters are richly described, so the description needn't explain return values or parameter details. For a read-only explainer it is essentially complete, though it could note how topic and name must be paired.

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% and every parameter including the topic/name/format enums is documented in the schema itself. The description only restates the topic list in prose, adding no syntax, format, or pairing semantics beyond what the schema provides.

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 clear resource (Bittensor concepts) and enumerates the covered domains, so an agent knows this is the explanation/documentation tool. It does not distinguish itself from siblings like subtensor_lookup or subtensor_explore, which an agent may plausibly confuse it with.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no mention of alternatives, and no condition that selects this tool over subtensor_lookup/subtensor_search. Usage is only implied by the verb 'Understand'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources