Skip to main content
Glama

Explore relationships and changelogs

subtensor_explore
Read-onlyIdempotent

Explore relationships, version history, removed items, changelogs, and migration guides between runtime versions.

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_explore"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoItem name (e.g., 'StakeAdded', 'add_stake', 'TotalStake')
typeNoItem type — for relationships (event/call/storage/error), for removed (all/pallet/event/call/storage/constant/error)
limitNoMax items per page (default: 10)
topicYesWhat to explore
cursorNoPagination cursor from previous response
formatNoResponse format: 'text' (compact, default) or 'json' (structured)
palletNoPallet name (e.g., 'SubtensorModule')
versionNoFor versions: look up a specific version
to_versionNoFor changelog/migration: end version
from_versionNoFor changelog/migration: start version

Output Schema

NameRequiredDescriptionDefault
topicYesExplore topic, mirrors the request topic

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds the enumeration of explored concepts, which is useful context but largely restates the topic enum; it says nothing about pagination, rate limits, or cross-version behavior.

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 with no filler; the list of explored concepts is dense and each item earns its place. It could be tightened, but nothing is padding.

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?

This is a multi-mode tool with 10 parameters, 8 topic values, and 7 type values, yet the description never explains which parameters apply to which topic. Output schema coverage means return values need no explanation, but the mode-selection complexity is left entirely undocumented.

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 all ten parameters are already documented, including per-topic applicability. The description adds no syntax, defaults, or constraints beyond what the schema provides, so the baseline 3 applies.

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?

The description gives a clear verb (explore) plus the specific resources it covers — relationships, version history, removed items, changelogs, migration guides — which maps well onto the topic enum. However, it does not differentiate itself from siblings like subtensor_lookup or subtensor_search, leaving overlap ambiguity.

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 guidance on when to choose this tool over subtensor_lookup, subtensor_search, or subtensor_list, nor any indication that the required 'topic' parameter switches the tool's mode of operation. The agent must infer all routing decisions.

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