Skip to main content
Glama
dappros

Ethora MCP Server

by dappros

ethora-wallet-get-balance

Retrieve the authenticated user’s cryptocurrency wallet balance directly within the Ethora platform. Simplify balance checking for integrated applications and services.

Instructions

Retrieve the cryptocurrency wallet balance of the authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'ethora-wallet-get-balance' tool. It asynchronously calls walletGetBalance(), formats the response as a CallToolResult with JSON content, or returns an error message on failure.
    async function () {
        try {
            let result = await walletGetBalance()
            let toolRes: CallToolResult = {
                content: [{ type: "text", text: JSON.stringify(result.data) }]
            }
            return toolRes
        } catch (error) {
            let toolRes: CallToolResult = {
                content: [{ type: "text", text: "error: network error" }]
            }
            return toolRes
        }
    }
  • src/tools.ts:289-310 (registration)
    Registers the 'ethora-wallet-get-balance' tool on the MCP server using server.registerTool, specifying the tool name, description (no input schema), and the handler function.
    function walletGetBalanceTool(server: McpServer) {  
        server.registerTool(
            'ethora-wallet-get-balance',
            {
                description: 'Retrieve the cryptocurrency wallet balance of the authenticated user'
            },
            async function () {
                try {
                    let result = await walletGetBalance()
                    let toolRes: CallToolResult = {
                        content: [{ type: "text", text: JSON.stringify(result.data) }]
                    }
                    return toolRes
                } catch (error) {
                    let toolRes: CallToolResult = {
                        content: [{ type: "text", text: "error: network error" }]
                    }
                    return toolRes
                }
            }
        )
    }
  • Helper function that performs the actual API call to retrieve the wallet balance via GET /wallets/balance using the configured axios client.
    export function walletGetBalance() {
      return httpClientDappros.get(
        `/wallets/balance`
      )
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions authentication but does not detail how authentication is handled, potential rate limits, error conditions, or the format of the returned balance. This leaves significant gaps in understanding the tool's behavior.

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 a single, clear sentence that efficiently conveys the core functionality without unnecessary words. It is front-loaded with the main action and resource, making it easy for an AI agent to parse 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's simplicity (0 parameters, no output schema, no annotations), the description is adequate but not fully complete. It covers the basic purpose but lacks details on authentication mechanisms, return format, or error handling, which could be important for an AI agent to use it correctly in context.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not add parameter details, earning a high score as it avoids redundancy and focuses on the tool's purpose.

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 action ('Retrieve') and resource ('cryptocurrency wallet balance of the authenticated user'), making the purpose evident. However, it does not explicitly differentiate from sibling tools like 'ethora-wallet-erc20-transfer', which is a related but distinct operation, so it falls short of 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 implies usage for authenticated users but provides no explicit guidance on when to use this tool versus alternatives, such as distinguishing it from other wallet-related tools or specifying prerequisites like authentication status. This lack of context reduces its helpfulness for an AI agent.

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/dappros/ethora-mcp-cli'

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