Skip to main content
Glama

send_edu

Transfer EDU native tokens securely to any wallet address by specifying the sender's private key, recipient address, and token amount. Simplify blockchain transactions and manage token distribution effectively.

Instructions

Send EDU native token to another wallet address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesAmount of EDU to send
privateKeyYesPrivate key of the sender wallet
toAddressYesRecipient wallet address

Implementation Reference

  • The core handler function that executes the EDU token transfer using ethers.js Wallet and Provider.
    export async function sendEdu(
      privateKey: string,
      toAddress: string,
      amount: string
    ): Promise<{
      hash: string,
      from: string,
      to: string,
      amount: string
    }> {
      try {
        const provider = getProvider();
        const wallet = new ethers.Wallet(privateKey, provider);
        
        // Convert amount to wei
        const amountWei = ethers.parseEther(amount);
        
        // Create and send transaction
        const tx = await wallet.sendTransaction({
          to: toAddress,
          value: amountWei
        });
        
        // Wait for transaction to be mined
        const receipt = await tx.wait();
        
        if (!receipt) {
          throw new Error('Transaction failed');
        }
        
        return {
          hash: tx.hash,
          from: wallet.address,
          to: toAddress,
          amount
        };
      } catch (error) {
        console.error('Error sending EDU:', error);
        throw error;
      }
    }
  • Input schema definition for the 'send_edu' tool, including parameters and validation.
      name: 'send_edu',
      description: 'Send EDU native token to another wallet address',
      inputSchema: {
        type: 'object',
        properties: {
          privateKey: {
            type: 'string',
            description: 'Private key of the sender wallet',
          },
          toAddress: {
            type: 'string',
            description: 'Recipient wallet address',
          },
          amount: {
            type: 'string',
            description: 'Amount of EDU to send',
          },
        },
        required: ['privateKey', 'toAddress', 'amount'],
      },
    },
  • src/index.ts:1017-1050 (registration)
    MCP tool call handler for 'send_edu' that validates inputs, calls the blockchain.sendEdu function, and formats the response.
    case 'send_edu': {
      if (!args.privateKey || typeof args.privateKey !== 'string') {
        throw new McpError(ErrorCode.InvalidParams, 'Private key is required');
      }
      
      if (!args.toAddress || typeof args.toAddress !== 'string') {
        throw new McpError(ErrorCode.InvalidParams, 'Recipient address is required');
      }
      
      if (!args.amount || typeof args.amount !== 'string') {
        throw new McpError(ErrorCode.InvalidParams, 'Amount is required');
      }
      
      // Get wallet address from private key for information
      const fromAddress = blockchain.getWalletAddressFromPrivateKey(args.privateKey);
      
      // Proceed with the transaction
      const result = await blockchain.sendEdu(args.privateKey, args.toAddress, args.amount);
      
      // Add from address to the result for better context
      const enhancedResult = {
        ...result,
        fromAddress
      };
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(enhancedResult, null, 2),
          },
        ],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It fails to disclose critical behavioral traits: this is a write operation (sending tokens implies mutation), requires authentication via private key, involves irreversible transfer of funds, and may have network fees or rate limits. The description is minimal and misses key safety and operational details.

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 with zero waste. It front-loads the core action and resource, making it immediately understandable. Every word earns its place, and there is no redundant or verbose phrasing.

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?

Given the complexity (a financial transaction tool with no annotations and no output schema), the description is incomplete. It omits critical context: irreversible nature, authentication requirements, potential errors, return values, or relationship to sibling tools. For a tool handling sensitive operations like token transfers, this leaves significant gaps for an AI agent.

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%, so parameters are fully documented in the schema. The description adds no additional meaning beyond implying 'EDU' relates to the 'amount' parameter. It doesn't clarify parameter interactions, units (e.g., decimals for amount), or validation rules. Baseline 3 is appropriate as the schema handles the heavy lifting.

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 ('send') and resource ('EDU native token') with the target ('to another wallet address'). It distinguishes from siblings like 'send_erc20_token' by specifying 'native token' rather than ERC20 tokens, though it doesn't explicitly contrast them. The purpose is specific and unambiguous.

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 is provided on when to use this tool versus alternatives like 'send_erc20_token' or 'swap_edu_for_tokens'. The description lacks context about prerequisites (e.g., needing sufficient balance) or exclusions. It merely states what it does without advising on its application.

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/SailFish-Finance/educhain-ai-agent-kit'

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