Skip to main content
Glama
Zetrix-Chain

Zetrix MCP Server

Official
by Zetrix-Chain

zetrix_get_account_base

Retrieve basic account information for a Zetrix blockchain address, providing essential details without assets or metadata.

Instructions

Get basic account information without assets and metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe Zetrix account address

Implementation Reference

  • Core handler function that executes the tool logic by querying the Zetrix RPC endpoint /getAccountBase for basic account details (address, balance, nonce). Handles API errors and response parsing.
    async getAccountBase(address: string): Promise<ZetrixAccountBase> {
      try {
        const response = await this.client.get("/getAccountBase", {
          params: { address },
        });
    
        if (response.data.error_code !== 0) {
          throw new Error(
            response.data.error_desc || `API Error: ${response.data.error_code}`
          );
        }
    
        return response.data.result;
      } catch (error) {
        if (axios.isAxiosError(error)) {
          throw new Error(`Failed to get account base: ${error.message}`);
        }
        throw error;
      }
    }
  • MCP server handler (switch case) that receives tool calls, extracts the address argument, invokes ZetrixClient.getAccountBase(), and formats the response as MCP content.
    case "zetrix_get_account_base": {
      if (!args) {
        throw new Error("Missing arguments");
      }
      const result = await zetrixClient.getAccountBase(args.address as string);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • src/index.ts:141-154 (registration)
    Tool registration in the MCP tools array, including name, description, and input schema requiring an 'address' string.
    {
      name: "zetrix_get_account_base",
      description: "Get basic account information without assets and metadata",
      inputSchema: {
        type: "object",
        properties: {
          address: {
            type: "string",
            description: "The Zetrix account address",
          },
        },
        required: ["address"],
      },
    },
  • TypeScript interface defining the structure of the account base response (address, balance, nonce, optional priv).
    export interface ZetrixAccountBase {
      address: string;
      balance: string;
      nonce: number;
      priv?: any;
    }
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 mentions the tool is a read operation ('Get') and specifies content exclusions, but lacks critical behavioral details: whether it requires authentication, rate limits, error conditions, or response format. For a read tool with zero annotation coverage, this is insufficient.

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 and key limitation. Every word earns its place with zero redundancy or fluff.

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?

For a simple read tool with 1 parameter (fully documented in schema) but no annotations or output schema, the description is minimally adequate. It clarifies scope vs. siblings, but lacks behavioral context (auth, errors, response format) that would be needed for robust agent usage.

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 description coverage is 100% (the 'address' parameter is fully documented in the schema), so the baseline is 3. The description adds no parameter-specific information beyond what the schema already provides, but doesn't need to compensate for gaps.

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 verb ('Get') and resource ('basic account information') with a specific scope limitation ('without assets and metadata'). It distinguishes from sibling tools like 'zetrix_get_account' (likely full account info) and 'zetrix_get_account_assets'/'zetrix_get_account_metadata' (specific components), but doesn't explicitly name these alternatives.

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 context by specifying what's excluded ('without assets and metadata'), suggesting this tool is for lightweight account overviews. However, it doesn't provide explicit when-to-use guidance, prerequisites, or direct comparisons with alternatives like 'zetrix_get_account' or 'zetrix_get_balance'.

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