Skip to main content
Glama

list_wallets

List managed public wallet addresses and real-time balances across chains to monitor holdings and confirm approved destinations before DeFi interactions.

Instructions

List managed public wallet addresses and real-time balances across chains.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden and it does disclose two useful traits: results are limited to wallets the service 'manages' (not arbitrary addresses) and balances are fetched in real time, implying live network calls rather than cached data. It does not state whether the operation is read-only, whether it requires auth, how many wallets may be returned, or whether zero-balance wallets are included.

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?

A single front-loaded sentence with no filler; every element (managed, public addresses, real-time balances, across chains) adds information.

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 zero-parameter list tool with no output schema, the description adequately conveys what comes back (addresses plus balances, multi-chain). It would be fully complete with a note on result size/ordering or that no filtering options exist, but no serious gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. One small missed opportunity is noting that no chain or wallet filter is available, which an agent might otherwise assume it could pass.

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 specific verb and resource (list managed public wallet addresses) plus the payload (real-time balances across chains), so it is immediately distinguishable from siblings like list_whitelisted_contracts or transfer_crypto. It stops short of explicitly naming what it is not, which is what separates a 4 from a 5.

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 when-to-use guidance, no statement of prerequisites (e.g. authentication or a configured wallet provider), and no mention of when an agent should prefer transfer_crypto or list_whitelisted_contracts instead. Usage is only implied by the verb 'List'.

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