Skip to main content
Glama

Look up Subtensor item

subtensor_lookup
Read-onlyIdempotent

Get detailed info about a specific pallet, event, call, storage item, constant, error, SCALE type, RPC method, protocol account, or EVM precompile. Accepts URN identifiers with optional #field.path drilling.

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

Input Schema

NameRequiredDescriptionDefault
subNoFor type="account": derive a sub-account. A number is a netuid or crowdloan id; a string is an 8-byte tag such as "beta/esc". Index 0 collapses onto the base address.
urnNoURN identifier (e.g., 'subtensor:event:SubtensorModule.StakeAdded', 'subtensor:storage:System.Account#data.free', 'subtensor:api:SwapRuntimeApi.sim_swap_tao_for_alpha', 'subtensor:account:SubtensorModule.SubtensorPalletId#64', 'subtensor:precompile:StakingV2'). `subtensor:runtime_api:...` is accepted as an alias for `subtensor:api:...`. Supports field-path drilling with # for event/call/storage/type items (for account items, #fragment is a sub-index instead). Alternative to type+pallet+name. Takes precedence if both provided.
nameNoItem name (e.g., 'SubtensorModule', 'StakeAdded', 'add_stake', 'AccountId32', 'pruning', 'pow-faucet') or type ID number. For type="account": the declaring key ('SubtensorModule.SubtensorPalletId'). For type="precompile": a name ('StakingV2') or 0x address.
typeNoWhat kind of item to look up
formatNoResponse format: 'text' (compact, default) or 'json' (structured)
palletNoPallet name — required for event/call/storage/constant/error lookups (e.g., 'SubtensorModule')
addressNoFor type="account": an SS58 address to identify. Returns which protocol account it is, including the sub-index, or reports that it is an ordinary wallet.
includeNoFor pallet lookup: filter to a specific item type with descriptions
languageNoField name casing for your language. TypeScript shows camelCase (tickLow), others show snake_case (tick_low). Overrides session preference.
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.
include_historyNoInclude full argument signatures for each version range (events/calls only)
include_removedNoInclude removed/historical items (default: false)

Output Schema

NameRequiredDescriptionDefault
nameYes
typeYesItem kind, mirrors the request type
palletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered and the description is free to add resolution semantics instead: URN-vs-explicit-arg precedence, the runtime_api alias, and #field.path drilling. It adds real behavior beyond the annotations, though it says nothing about result size, pagination, or failure when an item is unknown (an output schema exists, which covers the return shape).

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?

Two sentences, both front-loaded: the first leads with the action and the item kinds, the second leads with the accepted identifier form and its extension. Nothing is padding, and the enumeration is necessary because the tool spans many item kinds.

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 a full input schema, an output schema, and rich annotations, the description only needs to add resolution behavior, and it does. The remaining gap is orientation within the tool family: with six siblings and 12 all-optional parameters, a sentence on which combinations to reach for would make it self-sufficient.

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 the schema itself is unusually rich (examples, enums, per-parameter conditions), so the baseline is 3. The description only restates the URN-plus-drilling concept already documented in the `urn` property and adds no extra meaning for the other 11 parameters.

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 verb ("Get detailed info") and an explicitly enumerated set of resources (pallet, event, call, storage, constant, error, SCALE type, RPC method, protocol account, EVM precompile), plus the URN identifier form. It is clear what the tool returns, but it never names or contrasts itself with the siblings (search, explore, list), so an agent cannot tell from this text alone when lookup beats search.

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?

Usage is only implied: "a specific ... item" suggests resolving a known identifier rather than discovering one, which is the natural dividing line against subtensor_search/subtensor_explore, but that is never stated. The one explicit routing note is internal ("Alternative to type+pallet+name. Takes precedence if both provided"), which helps parameter choice but not tool choice.

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