Skip to main content
Glama
armorwallet
by armorwallet

get_all_wallets

Retrieve a list of wallets and their associated assets, including balances, for blockchain operations. Specify whether to include archived wallets.

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 for get_all_wallets, decorated with @mcp.tool() for registration. Checks login and delegates to ArmorClient.
    @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)}]
  • Output schemas: WalletBalance, WalletInfo, and Wallet (inherits WalletInfo with balances list). Input uses ListWalletsRequest below.
    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")
  • Input schema: ListWalletsRequest Pydantic model defining the is_archived parameter.
    class ListWalletsRequest(BaseModel):
        is_archived: bool = Field(default=False, description="whether to include archived wallets")
  • Core helper method in ArmorClient that performs the API GET call to retrieve wallets based on is_archived flag.
    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}")
  • @mcp.tool() decorator registers the get_all_wallets function as an MCP tool.
    @mcp.tool()
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 retrieval and returns a list, but lacks details on permissions, rate limits, pagination, or error handling. For a read operation with no annotations, this is insufficient behavioral disclosure.

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?

Two sentences with zero waste, front-loaded with the main action. However, it's slightly under-specified given the lack of detail, but not verbose or poorly structured.

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 no annotations, 1 parameter with 0% schema coverage, and an output schema exists, the description is minimally adequate. It states the action and return type but misses key context like parameter meaning, behavioral traits, and sibling differentiation, making it incomplete for optimal agent use.

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 0%, so the description must compensate. It adds no parameter information beyond what the schema provides (e.g., 'is_archived' parameter). With 1 parameter and no description of it, this meets the baseline for minimal coverage but doesn't enhance understanding.

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

Purpose3/5

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

The description states the tool retrieves wallets with balances, which is a clear purpose, but it's vague about scope and doesn't distinguish from siblings like 'get_wallet_token_balance' or 'list_groups'. It specifies 'all wallets' but doesn't clarify if this means all accessible wallets or all in existence.

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?

No guidance on when to use this tool versus alternatives. It doesn't mention siblings like 'get_wallet_token_balance' for specific balances or 'list_groups' for grouped wallets, nor does it provide context about prerequisites or typical use cases.

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

Related 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/armorwallet/armor-crypto-mcp'

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