Skip to main content
Glama

Holdings

holdings

Every token balance of ONE X1 wallet, read live from the X1 chain: native XNT plus SPL and Token-2022 accounts, with symbols. If a read fails the answer says it is incomplete; it never reports an empty wallet it could not read. For trading history use wallet_profile.

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": {
      "wallet": "<wallet>"
    },
    "name": "holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well on the most important risk: it discloses partial-failure semantics — a failed read is reported as incomplete rather than a false empty wallet. That is exactly the kind of behavior an agent would otherwise misread. It stops short of stating rate limits, latency, or whether results are cached, which keeps it out of 5 territory.

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?

Three tightly packed sentences, front-loaded with what is returned before the failure caveat and the sibling redirect. Nearly every clause earns its place; the 'read live from the X1 chain' phrasing is slightly redundant with 'every token balance of ONE X1 wallet' but also signals freshness.

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?

There is no output schema, so the description properly specifies the content of the response (balances across three token standards, with symbols) and the partial-failure representation. For a one-parameter read tool this is close to complete; it lacks only guidance on result size or pagination for wallets with many token accounts.

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 coverage is 0%, so the description must compensate. It adds the meaningful constraint that the argument is a single X1-chain wallet (not a list, not arbitrary EVM), which narrows interpretation of the lone 'wallet' param. However, it never states the address format, chain validation behavior, or what happens with a malformed/invalid address.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (read balances live) and resource (ONE X1 wallet), enumerates the exact asset classes covered (native XNT, SPL, Token-2022) plus the symbol enrichment, and explicitly differentiates itself from wallet_profile. An agent can pick this over arc_wallet, arc_holders, or evm_balances_bulk without opening any schema.

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

Usage Guidelines4/5

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

It states the use case (balance snapshot of a single X1 wallet) and routes trading-history queries to wallet_profile, which covers the main confusion risk. It doesn't say what to do if the agent has an EVM address or a multi-wallet question, so the exclusions are only partial.

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