Skip to main content
Glama
Jake-loranger

Algorand MCP Server

generate_algorand_account

Create a new Algorand blockchain account with a unique address and mnemonic for secure access and transactions.

Instructions

Generate a new Algorand account with address and mnemonic

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function in AlgorandService class that generates a new Algorand account using algosdk.generateAccount() and derives the mnemonic from the secret key.
    generateAccount(): { account: algosdk.Account; mnemonic: string } {
        const account = algosdk.generateAccount();
        const mnemonic = algosdk.secretKeyToMnemonic(account.sk);
    
        return { account, mnemonic };
    }
  • MCP server tool execution handler (switch case) that parses arguments, calls algorandService.generateAccount(), and formats the response.
    case 'generate_algorand_account': {
        GenerateAccountArgsSchema.parse(args);
        try {
            const { account, mnemonic } = algorandService.generateAccount();
            return {
                content: [
                    {
                        type: 'text',
                        text: `New Algorand Account Generated:\nAddress: ${account.addr}\nMnemonic: ${mnemonic}\n\n⚠️ SECURITY WARNING: Store the mnemonic phrase securely and never share it. This is required to access your account.`,
                    },
                ],
            };
        } catch (error) {
            return {
                content: [
                    {
                        type: 'text',
                        text: `Error generating account: ${error}`,
                    },
                ],
                isError: true,
            };
        }
    }
  • Zod schema definition for generate_algorand_account tool input arguments (empty object, no parameters).
    const GenerateAccountArgsSchema = z.object({});
  • src/index.ts:156-164 (registration)
    Tool registration entry in the TOOLS array, specifying name, description, and input schema for MCP server.
    {
        name: 'generate_algorand_account',
        description: 'Generate a new Algorand account with address and mnemonic',
        inputSchema: {
            type: 'object',
            properties: {},
            required: [],
        },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool generates an account but doesn't disclose behavioral traits like whether this is a local or on-chain operation, security implications, or what happens to existing accounts. This is a significant gap for a tool that likely creates sensitive data.

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 front-loads the core purpose. Every word earns its place with no waste or redundancy.

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 account generation (likely involving cryptographic operations and sensitive outputs), no annotations, and no output schema, the description is incomplete. It should explain what the generated account includes, security notes, or how to use the output with other tools.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the inputs. The description doesn't need to add parameter details, and it correctly doesn't mention any. Baseline is 4 for zero-parameter tools.

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 specific action ('Generate a new Algorand account') and the resources produced ('with address and mnemonic'). It distinguishes from sibling tools like 'load_wallet' or 'store_wallet' by focusing on creation rather than management.

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 implies usage when a new account is needed, but it doesn't explicitly state when to use this tool versus alternatives like 'fund_testnet' or 'load_wallet'. No guidance on prerequisites or exclusions is provided.

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/Jake-loranger/algorand-mcp-server'

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