Skip to main content
Glama
Zetrix-Chain

Zetrix MCP Server

Official
by Zetrix-Chain

zetrix_sdk_create_account

Generate a new blockchain account on Zetrix using the official SDK to enable secure transactions and smart contract interactions.

Instructions

Create a new Zetrix account using the official SDK

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP server handler for the 'zetrix_sdk_create_account' tool. Dispatches the request by calling ZetrixSDK.createAccount() and returns the result as JSON.
    case "zetrix_sdk_create_account": {
      const account = await zetrixSDK.createAccount();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(account, null, 2),
          },
        ],
      };
    }
  • src/index.ts:420-427 (registration)
    Tool registration in the tools array used by ListToolsRequestHandler. Defines name, description, and empty input schema.
    {
      name: "zetrix_sdk_create_account",
      description: "Create a new Zetrix account using the official SDK",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Core implementation of account creation in ZetrixSDK wrapper class. Initializes SDK and calls official zetrix-sdk-nodejs account.create() method to generate new keypair and address.
    async createAccount(): Promise<ZetrixSDKAccount> {
      await this.initSDK();
    
      try {
        const result = await this.sdk.account.create();
    
        if (result.errorCode !== 0) {
          throw new Error(result.errorDesc || `SDK Error: ${result.errorCode}`);
        }
    
        return {
          address: result.result.address,
          privateKey: result.result.privateKey,
          publicKey: result.result.publicKey,
        };
      } catch (error) {
        throw new Error(
          `Failed to create account: ${error instanceof Error ? error.message : String(error)}`
        );
      }
    }
  • TypeScript interface defining the output structure of the createAccount method.
    export interface ZetrixSDKAccount {
      address: string;
      privateKey: string;
      publicKey: string;
    }
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. It implies a write operation ('Create') but doesn't disclose behavioral traits like whether this requires authentication, what happens on failure (e.g., error handling), or if it has side effects like generating keys. The description is minimal and misses critical operational details.

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 no wasted words. It front-loads the key action ('Create a new Zetrix account') and adds necessary context ('using the official SDK'), making it highly concise and well-structured.

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 creation (a write operation with potential side effects), no annotations, and no output schema, the description is inadequate. It lacks details on success/failure outcomes, error handling, or any behavioral context, leaving significant gaps for an AI agent to use it correctly.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is acceptable here, but it could have mentioned if any implicit parameters (like SDK context) are required, though not strictly necessary.

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') and resource ('new Zetrix account'), and specifies the method ('using the official SDK'). It distinguishes from sibling tools like 'zetrix_create_keypair' by focusing on account creation rather than key generation, though it doesn't explicitly contrast with all siblings.

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?

No guidance is provided on when to use this tool versus alternatives like 'zetrix_create_keypair' or 'zetrix_get_account'. The description lacks context about prerequisites, such as needing SDK setup or network connectivity, and doesn't mention when not to use it.

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/Zetrix-Chain/zetrix-mcp-server'

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