Skip to main content
Glama
monad-vibe

Monad MCP Server

by monad-vibe

send-mon-transaction

Initiate MON token transfers on the Monad testnet by specifying recipient addresses and transaction amounts using this MCP server tool.

Instructions

Send MON transaction on Monad testnet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesAmount of MON to send
toYesRecipient address

Implementation Reference

  • The core handler function that executes the tool: creates wallet client, sends transaction to recipient with parsed ether amount, returns success with tx hash or error message.
    async ({ to, amount }) => {
        try {
            // Create wallet client
            const client = await createWallet();
    
            // Send transaction
            const hash = await client.sendTransaction({
                to: to as `0x${string}`,
                value: parseEther(amount),
            });
    
            return {
                content: [
                    {
                        type: "text",
                        text: `Transaction sent successfully! Hash: ${hash}`,
                    },
                ],
            };
        } catch (error) {
            return {
                content: [
                    {
                        type: "text",
                        text: `Failed to send transaction. Error: ${error instanceof Error ? error.message : String(error)}`,
                    },
                ],
            };
        }
    }
  • Input validation schema using Zod for recipient address and MON amount.
    {
        to: z.string().describe("Recipient address"),
        amount: z.string().describe("Amount of MON to send"),
    },
  • Registers the send-mon-transaction tool on the MCP server with name, description, schema, and handler function.
    export function sendMonProvider(server: McpServer) {
        server.tool(
            "send-mon-transaction",
            "Send MON transaction on Monad testnet",
            {
                to: z.string().describe("Recipient address"),
                amount: z.string().describe("Amount of MON to send"),
            },
            async ({ to, amount }) => {
                try {
                    // Create wallet client
                    const client = await createWallet();
    
                    // Send transaction
                    const hash = await client.sendTransaction({
                        to: to as `0x${string}`,
                        value: parseEther(amount),
                    });
    
                    return {
                        content: [
                            {
                                type: "text",
                                text: `Transaction sent successfully! Hash: ${hash}`,
                            },
                        ],
                    };
                } catch (error) {
                    return {
                        content: [
                            {
                                type: "text",
                                text: `Failed to send transaction. Error: ${error instanceof Error ? error.message : String(error)}`,
                            },
                        ],
                    };
                }
            }
        );
    }
  • Utility function to create a configured wallet client for Monad testnet from environment private key, used by the handler.
    export async function createWallet() {
      const privateKey = process.env.PRIVATE_KEY;
      if (!privateKey) {
        throw new Error('PRIVATE_KEY environment variable is not set');
      }
      const account = privateKeyToAccount(privateKey as `0x${string}`);
      const client = createWalletClient({ account, chain: monadTestnet, transport: http() });
      return client;
    }
  • src/index.ts:24-24 (registration)
    Top-level call to walletProvider during server initialization, which chains to sendMonProvider registration.
    walletProvider(server);
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 states the action but lacks critical details: it doesn't specify if this requires authentication, what the transaction cost or gas implications are, whether it's irreversible, or what the expected response format is. This is a significant gap for a transaction tool.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 of a transaction tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like authentication needs, error handling, or return values, leaving the agent with insufficient context to use the tool safely and effectively.

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?

The input schema has 100% description coverage, clearly documenting both parameters ('amount' and 'to'). The description adds no additional parameter semantics beyond what the schema provides, such as format details (e.g., address format, unit for amount) or constraints. Baseline 3 is appropriate as the schema does 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 MON transaction') and specifies the target environment ('on Monad testnet'), which distinguishes it from mainnet operations. However, it doesn't differentiate from potential sibling tools like 'deploy-mon-contract' that might also involve transactions, leaving room for improvement in sibling distinction.

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. It doesn't mention prerequisites (e.g., needing a wallet or balance), exclusions, or comparisons to sibling tools like 'deploy-mon-contract' for contract deployments or 'get-mon-balance' for checking funds 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/monad-vibe/monad-mcp-server'

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