Skip to main content
Glama
dappros

Ethora MCP Server

by dappros

ethora-wallet-erc20-transfer

Transfer ERC20 tokens between wallets on the Ethora platform by specifying the recipient address and the amount to send.

Instructions

Transfer ERC20 tokens to another wallet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesamount for transfer
toWalletYesto address for transfer

Implementation Reference

  • src/tools.ts:312-337 (registration)
    Registers the 'ethora-wallet-erc20-transfer' tool with MCP server, including schema and inline handler function that calls the API helper.
    function walletERC20TransferTool(server: McpServer) {
        server.registerTool(
            'ethora-wallet-erc20-transfer',
            {
                description: 'Transfer ERC20 tokens to another wallet',
                inputSchema: {
                    toWallet: z.string().describe("to address for transfer"),
                    amount: z.number().describe("amount for transfer"),
                }
            },
            async function ({ toWallet, amount }) {
                try {
                    let result = await walletERC20Transfer(toWallet, amount)
                    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
                }
            }
        )
    }
  • Core helper function that performs the ERC20 token transfer via POST request to the /tokens/transfer API endpoint.
    export function walletERC20Transfer(toWallet: string, amount: number) {
      return httpClientDappros.post(
        `/tokens/transfer`,
        {
          toWallet,
          amount,
          "tokenId": "ERC20",
          "tokenName": "Dappros Platform Token"
        }
      )
    }
  • src/tools.ts:339-352 (registration)
    Main entry point that calls walletERC20TransferTool to register the tool among others.
    export function registerTools(server: McpServer) {
        userLoginWithEmailTool(server);
        userRegisterWithEmailTool(server);
        appListTool(server);
        appCreateTool(server);
        appDeleteTool(server);
        appUpdateTool(server);
        appGetDefaultRoomsTool(server);
        craeteAppChatTool(server);
        appDeleteChatTool(server);
        getDefaultRoomsWithAppIdTool(server);
        walletGetBalanceTool(server);
        walletERC20TransferTool(server);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'transfer' implies a write/mutation operation, the description doesn't mention critical aspects like whether this requires authentication, gas fees, transaction confirmation time, irreversible nature of blockchain transactions, or potential rate limits.

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, efficient sentence that communicates the core functionality without any wasted words. It's appropriately sized for a simple transfer operation and gets straight to the point.

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

Completeness2/5

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

For a blockchain token transfer tool with no annotations and no output schema, the description is insufficient. It doesn't address authentication requirements, transaction costs, confirmation mechanisms, error scenarios, or what the tool returns. The description should provide more context given the complexity of blockchain operations.

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 100%, with both parameters clearly documented in the schema. The description doesn't add any meaningful parameter semantics beyond what's already in the schema (amount and toWallet). This meets the baseline for high schema coverage.

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 ('Transfer') and resource ('ERC20 tokens to another wallet'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'ethora-wallet-get-balance', but the verb+resource combination is specific enough for basic understanding.

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. There's no mention of prerequisites (like needing a wallet with sufficient balance), error conditions, or relationship to sibling tools like 'ethora-user-login' which might be required first.

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