Skip to main content
Glama

menese_setup

Create or import a Menese wallet for DeFi access. Generate new wallets, restore from existing seeds, or check current wallet status through the MCP server.

Instructions

Create or import a Menese wallet. Actions: 'new' generates a fresh wallet, 'import' restores from an existing hex seed, 'status' shows current wallet info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform
seedNo64-char hex seed (for 'import' action only)

Implementation Reference

  • The 'menese_setup' tool handler implementation, which manages wallet creation, import, and status retrieval using the provided seed or by generating a new one.
    server.registerTool(
      "menese_setup",
      {
        description:
          "Create or import a Menese wallet. Actions: 'new' generates a fresh wallet, " +
          "'import' restores from an existing hex seed, 'status' shows current wallet info.",
        inputSchema: {
          action: z.enum(["new", "import", "status"]).describe("Action to perform"),
          seed: z.string().length(64).optional().describe("64-char hex seed (for 'import' action only)"),
        },
      },
      async ({ action, seed: importSeed }) => {
        if (action === "status") {
          const current = store.get();
          if (!current) {
            return { content: [{ type: "text" as const, text: "No wallet configured. Use action 'new' to create one or 'import' to restore." }] };
          }
          const addrRes = await getAllAddresses(config, current.principal, current.seed);
          const evm = addrRes.ok ? (addrRes.data.evm?.evmAddress ?? "—") : "—";
          const sol = addrRes.ok ? (addrRes.data.solana?.address ?? "—") : "—";
          const btc = addrRes.ok ? (addrRes.data.bitcoin?.bech32Address ?? "—") : "—";
          return {
            content: [{
              type: "text" as const,
              text: JSON.stringify({
                principal: current.principal,
                eth: evm,
                sol,
                btc,
                agentCanisterId: current.agentCanisterId ?? null,
              }, null, 2),
            }],
          };
        }
    
        let seed: string;
        if (action === "import") {
          if (!importSeed || !/^[0-9a-fA-F]{64}$/.test(importSeed)) {
            return {
              content: [{ type: "text" as const, text: "Invalid seed. Expected 64 hex characters (32 bytes)." }],
              isError: true,
            };
          }
          seed = importSeed.toLowerCase();
        } else {
          seed = generateSeed();
        }
    
        const principal = getPrincipalFromSeed(seed);
        store.set({ seed, principal });
    
        const addrRes = await getAllAddresses(config, principal, seed);
        const evm = addrRes.ok ? (addrRes.data.evm?.evmAddress ?? "—") : "—";
        const sol = addrRes.ok ? (addrRes.data.solana?.address ?? "—") : "—";
        const btc = addrRes.ok ? (addrRes.data.bitcoin?.bech32Address ?? "—") : "—";
    
        return {
          content: [{
            type: "text" as const,
            text: JSON.stringify({
              status: action === "import" ? "Wallet imported" : "Wallet created",
              principal,
              eth: evm,
              sol,
              btc,
              seed: action === "new" ? seed : undefined,
            }, null, 2),
          }],
        };
      },
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. While it explains the three actions, it fails to disclose critical wallet-specific behaviors: whether 'new' overwrites existing wallets, where wallets are persisted, security implications of handling hex seeds, or what return values to expect.

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 sentences with zero waste: first states overall purpose, second efficiently maps the three action values to their specific behaviors. Information is front-loaded and every clause earns its place.

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 100% schema coverage and absence of output schema, the description adequately covers input parameters. However, for a wallet setup tool with no annotations, it lacks completeness regarding side effects (file system persistence), output expectations, and safety warnings about cryptographic material handling.

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?

With 100% schema coverage, the baseline is 3. The description adds value by explaining the semantic meaning of each enum value for the 'action' parameter (e.g., 'new' generates a fresh wallet), which helps the agent understand the operational impact of each choice beyond the schema's generic 'Action to perform'.

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

Purpose5/5

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

The description clearly states the tool 'Create[s] or import[s] a Menese wallet' with specific verbs and resource identification. It distinguishes from siblings (menese_send, menese_balance, etc.) by focusing on wallet initialization rather than operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description maps the three action values to their behaviors (new/generates, import/restores, status/shows), providing implicit usage guidance. However, it lacks explicit when-to-use guidance relative to sibling tools or prerequisites (e.g., whether to check status before creating new).

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