Skip to main content
Glama

get_all_wallets

Retrieve a complete list of cryptocurrency wallets with their current balances and assets for portfolio management and tracking across supported blockchain networks.

Instructions

Retrieve all wallets with balances.

Returns a list of Wallets and asssets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
get_all_wallets_requestsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler decorated with @mcp.tool(). Proxies the request to the ArmorWalletAPIClient's get_all_wallets method, handling authentication check and errors.
    @mcp.tool()
    async def get_all_wallets(get_all_wallets_requests: ListWalletsRequest) -> List[Wallet]:
        """
        Retrieve all wallets with balances.
        
        Returns a list of Wallets and asssets
        """
        if not armor_client:
            return [{"error": "Not logged in"}]
        try:
            result: List[Wallet] = await armor_client.get_all_wallets(get_all_wallets_requests)
            return result
        except Exception as e:
            return [{"error": str(e)}]
  • Pydantic models defining the input schema (ListWalletsRequest) and output schema (Wallet, extending WalletInfo with balances as List[WalletBalance]). Used for validation and typing.
    class ListWalletsRequest(BaseModel):
        is_archived: bool = Field(default=False, description="whether to include archived wallets")
    
    
    class WalletBalance(BaseModel):
        mint_address: str = Field(description="public mint address of output token. To get the address from a token symbol use `get_token_details`")
        name: str = Field(description="name of the token")
        symbol: str = Field(description="symbol of the token")
        decimals: int = Field(description="number of decimals of the token")
        amount: float = Field(description="balance of the token")
        usd_price: str = Field(description="price of the token in USD")
        usd_amount: float = Field(description="balance of the token in USD")
    
    
    class WalletInfo(BaseModel):
        id: str = Field(description="wallet id")
        name: str = Field(description="wallet name")
        is_archived: bool = Field(description="whether the wallet is archived")
        public_address: str = Field(description="public address of the wallet")
    
    
    class Wallet(WalletInfo):
        balances: List[WalletBalance] = Field(description="list of balances of the wallet")
  • Implementation of get_all_wallets in ArmorWalletAPIClient class. Performs the actual HTTP GET request to the Armor API endpoint `/wallets/?is_archived={data.is_archived}` using the shared _api_call method.
    async def get_all_wallets(self, data: ListWalletsRequest) -> List[Wallet]:
        """Return all wallets with balances."""
        return await self._api_call("GET", f"wallets/?is_archived={data.is_archived}")
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions returning 'a list of Wallets and assets', which gives basic output info, but lacks critical behavioral details: whether this is a read-only operation, if it requires authentication, any rate limits, pagination for large result sets, or error conditions. The misspelling 'asssets' undermines clarity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief (two sentences) but inefficiently structured. The first sentence states the purpose clearly, but the second is redundant with the output schema and contains a typo ('asssets'). It could be condensed into a single, error-free sentence without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 1 parameter with 0% schema coverage and an output schema (which handles return values), the description is minimally adequate but incomplete. It covers the basic purpose and output type but misses parameter documentation and behavioral context, making it insufficient for reliable tool invocation without external schema inspection.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions no parameters at all, despite there being 1 required parameter ('get_all_wallets_requests'). The description fails to explain what this parameter does, its expected format, or how it influences the retrieval, leaving the agent guessing.

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 clearly states the verb ('Retrieve') and resource ('all wallets with balances'), making the purpose understandable. It distinguishes from siblings like 'get_wallet_token_balance' (single wallet) and 'list_groups' (different resource). However, it doesn't explicitly differentiate from 'get_all_orders' or other list-style tools beyond the resource type.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for retrieving all wallets, or compare to siblings like 'list_groups' or 'get_wallet_token_balance' for specific needs. The agent must infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/emmaThompson07/armor-crypto-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server