Skip to main content
Glama

random-sui-account

Generate random SUI blockchain accounts for testing and development purposes, not intended for production or real-world transactions. Easily create one or multiple accounts as needed.

Instructions

Create random SUI account, do not use it in production.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numNo

Implementation Reference

  • The asynchronous callback method 'cb' that executes the core logic of the 'random-sui-account' tool: generates a random mnemonic, derives multiple keypairs from it, extracts account info, and returns JSON stringified account details.
    async cb(args: RandomAccountParams) {
      const accountInfos = [];
      const mnemonic = genRandomMnemonic();
    
      for (let i = 0; i < args.num; i++) {
        const keypair = getKeypairFromMnemonic(mnemonic, i);
        const accountInfo = getAccountInfoFromKeypair(keypair);
        accountInfos.push(accountInfo);
      }
    
      return this.createTextResponse(JSON.stringify(accountInfos));
    }
  • Zod schema defining the input parameters for the tool, with an optional 'num' parameter defaulting to 1.
    const randomAccountParamsSchema = z.object({
      num: z.number().default(1),
    });
  • The tool instance 'randomSuiAccountTool' is included in the default export array of all tools from src/tools/index.ts, likely used for overall tool registration.
    export default [
      faucetTool,
      suiBalanceTool,
      suiTransferTool,
      randomSuiAccountTool,
      genMnemonicTool,
      genSuiAccountsByMnemonicTool,
      getAccountInfoByPriKeyTool,
    ];
  • src/tools/index.ts:4-4 (registration)
    Import of the pre-instantiated RandomSuiAccountTool from its implementation file.
    import randomSuiAccountTool from './account/gen-random.js';
  • Imports helper functions from utils/keypair.js used in the handler for mnemonic generation and keypair derivation.
    import {
      genRandomMnemonic,
      getKeypairFromMnemonic,
      getAccountInfoFromKeypair,
    } from '../../utils/keypair.js';
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the production warning but lacks critical details: what exactly gets created (e.g., key pair, address, mnemonic?), whether this consumes resources or has rate limits, what the output format is, or if there are any security implications beyond the production warning.

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 extremely concise (two brief clauses) with zero wasted words. It front-loads the core purpose and follows with critical usage guidance. Every sentence earns its place by providing essential 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?

Given no annotations, 0% schema description coverage, and no output schema, the description is incomplete for a tool that creates financial/cryptographic assets. It misses details about what constitutes an 'account' in this context, output format, security considerations, and how this differs from sibling tools. The production warning is helpful but insufficient for full understanding.

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 input schema has 1 parameter with 0% description coverage, so the description must compensate. While it doesn't explicitly mention the 'num' parameter, the tool name and description imply creation of one or more accounts, and the default value of 1 in the schema provides some context. The description adds value by clarifying the random nature of generation, though it could explicitly note the parameter controls quantity.

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 ('Create random SUI account') and specifies the resource type. It distinguishes from siblings like 'gen_sui_accounts_by_mnemonic' by emphasizing randomness rather than mnemonic-based generation, though it doesn't explicitly contrast with all alternatives like 'faucet' or 'get_account_info_by_private_key'.

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 provides a clear warning about when NOT to use this tool ('do not use it in production'), which is valuable guidance. However, it doesn't specify when TO use it (e.g., for testing, development, or demonstration purposes) or mention alternatives like 'gen_sui_accounts_by_mnemonic' for more controlled account generation.

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/deanpluse/sui-mcp'

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