Skip to main content
Glama

get_can_delegated_max_size

Read-onlyIdempotent

Query the maximum TRX amount (in Sun) an address can currently delegate as BANDWIDTH or ENERGY under Stake 2.0.

Instructions

Get the maximum amount of TRX (in Sun) that an address can currently delegate as resources (BANDWIDTH or ENERGY) under Stake 2.0.

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>",
      "resource": "<resource>"
    },
    "name": "get_can_delegated_max_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesWallet address (Base58 or hex)
networkNoNetwork name. Defaults to mainnet.
resourceYesResource type to query (BANDWIDTH or ENERGY)

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.6/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, open-world, non-destructive query. The description adds useful domain context by specifying the return unit as Sun and the Stake 2.0 scope, but it does not describe dependencies such as available stake or failure conditions.

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?

The description is a single well-formed sentence with the resource, unit, and Stake 2.0 context front-loaded. There is no redundant or filler wording.

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 simple read-only query with full schema coverage and rich annotations, the description covers the essential return meaning and domain scope. It could be more complete by noting how this differs from sibling delegated-resource tools, but no critical invocation information is missing.

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 the address, network, and resource parameters are already documented in the schema. The description reinforces the BANDWIDTH/ENERGY resource distinction and the Sun unit, but adds no syntax or constraints beyond the schema.

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 states a specific verb and resource: it returns the maximum TRX amount an address can currently delegate as BANDWIDTH or ENERGY under Stake 2.0. This is clear enough to distinguish it from generic account or delegated-resource queries, though it does not name a sibling tool for direct contrast.

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 implied by the purpose: use it to find the current maximum delegatable amount for an address and resource type. However, it provides no explicit when-to-use guidance, prerequisites, or comparison with alternatives such as get_delegated_resource.

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