Skip to main content
Glama

get_delegated_resource_account_index_v2

Read-onlyIdempotent

Retrieves the Stake 2.0 delegated resource account index for an address, showing which accounts delegated to it and which accounts it delegated to.

Instructions

Get delegated resource account index for an address under Stake 2.0 (who delegated to this address and who this address delegated to).

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": {
      "address": "<address>"
    },
    "name": "get_delegated_resource_account_index_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesWallet address (Base58 or hex)
networkNoNetwork name. Defaults to mainnet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.7

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that the result covers delegation in both directions, but says nothing about how the 'index' is shaped, pagination, or network-specific behavior beyond the default.

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 sentence with the resource first and the clarifying parenthetical second — front-loaded and free of filler. Only minor redundancy comes from restating the tool name almost verbatim before adding value.

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?

For a two-parameter read-only lookup with no output schema, the definition covers scope (Stake 2.0) and the bidirectional semantics of the result, which is what an agent needs to select it. Annotations handle the safety profile, so remaining gaps are minor.

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 both parameters (address, network) are documented there, including Base58/hex formats and the mainnet default. The description contributes no additional parameter meaning, which is acceptable at full coverage and justifies the baseline 3.

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?

Names a specific verb (Get) and resource (delegated resource account index) and clarifies the resource's meaning with a parenthetical: who delegated to this address and who it delegated to. The 'under Stake 2.0' qualifier implicitly separates it from the Stake 1.0 flavored get_delegated_resource_index sibling, but no sibling is named explicitly.

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 context is implied by the 'Stake 2.0' qualifier and the bidirectional explanation, which hints the agent should pick this over Stake 1.0 variants. There is no explicit when-to-use/when-not-to-use statement or named alternative, so guidance remains inferential.

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

Deploy Server

Other Tools