Skip to main content
Glama

menese_send

Send native tokens across 19 blockchains including Ethereum, Bitcoin, and Solana. Preview fees or execute transfers directly to recipient addresses.

Instructions

Send native tokens on any supported blockchain. Supports 19 chains: Ethereum, Polygon, Arbitrum, Base, Optimism, BNB, Bitcoin, Solana, ICP, SUI, TON, XRP, Litecoin, Cardano, Tron, Aptos, NEAR, CloakCoin, Thorchain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYesTarget blockchain
toYesRecipient address
amountYesAmount to send (decimal, e.g. '0.5')
tokenNoToken symbol (for ICRC-1 or ERC-20; omit for native token)
modeNo'quote' to preview fees, 'execute' to send. Default: execute

Implementation Reference

  • The async handler function for the "menese_send" tool, which processes token sending requests, including quote/execute logic and guard checks.
    async ({ chain, to, amount, token, mode }) => {
      const identity = store.get();
      if (!identity) {
        return { content: [{ type: "text" as const, text: "No wallet configured. Use menese_setup first." }], isError: true };
      }
    
      const guard = checkGuard("menese_send", { chain, to, amount, token, mode }, config);
      if (!guard.allowed) {
        return { content: [{ type: "text" as const, text: guard.reason! }], isError: true };
      }
    
      if (mode === "quote") {
        return {
          content: [{
            type: "text" as const,
            text: `Ready to send ${amount} ${token ?? "native"} on ${chain} to ${to}. Call again with mode "execute" to confirm.`,
          }],
        };
      }
    
      const result = await sendToken(config, resolveActorIdentity(store), chain, to, amount, { token });
    
      if (result.ok) {
        invalidateBalanceCaches(store.getPrincipal()!);
      }
    
      return {
        content: [{
          type: "text" as const,
          text: JSON.stringify(result, bigIntReplacer, 2),
        }],
      };
    },
  • The input schema definition and tool registration block for "menese_send" within the registerSendTool function.
    {
      description:
        "Send native tokens on any supported blockchain. Supports 19 chains: " +
        "Ethereum, Polygon, Arbitrum, Base, Optimism, BNB, Bitcoin, Solana, ICP, " +
        "SUI, TON, XRP, Litecoin, Cardano, Tron, Aptos, NEAR, CloakCoin, Thorchain.",
      inputSchema: {
        chain: z.enum(SUPPORTED_CHAINS as unknown as [string, ...string[]]).describe("Target blockchain"),
        to: z.string().describe("Recipient address"),
        amount: z.string().describe("Amount to send (decimal, e.g. '0.5')"),
        token: z.string().optional().describe("Token symbol (for ICRC-1 or ERC-20; omit for native token)"),
        mode: z.enum(["quote", "execute"]).optional()
          .describe("'quote' to preview fees, 'execute' to send. Default: execute"),
      },
    },
Behavior2/5

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

No annotations provided, yet the description fails to disclose critical behavioral traits of this high-stakes financial operation: irreversibility, gas/transaction fees, confirmation times, or authentication requirements. Simply stating 'Send' does not adequately warn of destructive side effects.

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?

Two well-structured sentences with zero waste: first establishes the action, second enumerates supported chains. Efficiently front-loaded with the most critical information.

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 financial transaction tool with 5 parameters and no output schema or annotations, the description is dangerously incomplete. It omits fee structures, error handling, return values, and prerequisites (e.g., wallet setup) that are essential for safe invocation.

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 has 100% description coverage, establishing baseline 3. The description enumerates the 19 supported chains, which mirrors the enum in the schema without adding semantic depth to parameter usage (e.g., address formats, amount precision rules).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific verb (send) and resource (tokens) with explicit chain enumeration, but inaccurately limits scope to 'native tokens' when the schema supports ERC-20/ICRC-1 via the optional 'token' parameter, potentially misleading users about the tool's full capability.

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?

Provides no guidance on when to use this tool versus siblings like 'menese_swap' or 'menese_quote', and fails to explain when to use 'quote' mode versus 'execute' mode despite the schema offering both 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/Aboodtt404/mcp-menese-sdk'

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