Skip to main content
Glama

get_account_info

Retrieve account address and native token balances across all supported EVM chains for cross-chain trading operations on Paloma DEX.

Instructions

Get account information including address and balances across all chains.

Returns:
    JSON string with account address and native token balances on all supported chains.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function decorated with @mcp.tool() that implements the get_account_info tool. It fetches the server's account address and native token balances (ETH equivalents) across all configured EVM chains using Web3 clients, returning formatted JSON.
    @mcp.tool()
    async def get_account_info(ctx: Context) -> str:
        """Get account information including address and balances across all chains.
        
        Returns:
            JSON string with account address and native token balances on all supported chains.
        """
        try:
            paloma_ctx = ctx.request_context.lifespan_context
            
            account_info = {
                "address": paloma_ctx.address,
                "balances": {}
            }
            
            for chain_id, config in CHAIN_CONFIGS.items():
                if chain_id in paloma_ctx.web3_clients:
                    try:
                        web3 = paloma_ctx.web3_clients[chain_id]
                        balance_wei = web3.eth.get_balance(paloma_ctx.address)
                        balance_eth = web3.from_wei(balance_wei, 'ether')
                        
                        account_info["balances"][config.name] = {
                            "native_balance": str(balance_eth),
                            "chain_id": config.chain_id,
                            "symbol": "ETH" if chain_id == ChainID.ETHEREUM_MAIN else config.name.split()[0]
                        }
                    except Exception as e:
                        account_info["balances"][config.name] = {"error": str(e)}
            
            return json.dumps(account_info, indent=2)
            
        except Exception as e:
            logger.error(f"Error getting account info: {e}")
            return f"Error getting account info: {str(e)}"
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes the return format ('JSON string with account address and native token balances on all supported chains'), which is helpful. However, it lacks details on potential errors, rate limits, authentication requirements, or whether this is a read-only operation (though implied by 'Get'). The description adds some value but leaves gaps in behavioral context.

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 highly concise and well-structured. It uses two sentences: the first states the tool's purpose, and the second specifies the return format. Every sentence adds value without redundancy, making it easy to parse and understand quickly.

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 the tool has no parameters, no annotations, and no output schema, the description provides a basic but incomplete picture. It explains what the tool returns, which is essential, but lacks details on error handling, authentication, or how it differs from sibling tools. For a read operation in a context with many similar tools, more guidance would improve completeness.

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 has 0 parameters, and schema description coverage is 100%. With no parameters to document, the description appropriately focuses on the tool's output. It adds meaningful context about what information is returned, which compensates for the lack of parameter details. This meets the baseline expectation for a parameterless tool.

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 tool's purpose: 'Get account information including address and balances across all chains.' It specifies the verb ('Get'), resource ('account information'), and scope ('across all chains'). However, it doesn't explicitly differentiate from sibling tools like 'get_address_balances' or 'get_address_balance_single_chain', which prevents a perfect score.

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. With sibling tools like 'get_address_balances' and 'get_address_balance_single_chain' available, there's no indication of how this tool differs in scope or use case. The description only states what it does, not when it should be selected over other options.

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/VolumeFi/mcpPADEX'

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