Skip to main content
Glama
Zetrix-Chain

Zetrix MCP Server

Official
by Zetrix-Chain

zetrix_sdk_is_activated

Check if a Zetrix blockchain account is activated by verifying its status with the provided address.

Instructions

Check if an account is activated on the blockchain

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe Zetrix account address

Implementation Reference

  • Tool schema definition including name, description, and input validation schema.
    {
      name: "zetrix_sdk_is_activated",
      description: "Check if an account is activated on the blockchain",
      inputSchema: {
        type: "object",
        properties: {
          address: {
            type: "string",
            description: "The Zetrix account address",
          },
        },
        required: ["address"],
      },
    },
  • src/index.ts:442-455 (registration)
    Tool registration in the tools array used by ListToolsRequestSchema handler.
    {
      name: "zetrix_sdk_is_activated",
      description: "Check if an account is activated on the blockchain",
      inputSchema: {
        type: "object",
        properties: {
          address: {
            type: "string",
            description: "The Zetrix account address",
          },
        },
        required: ["address"],
      },
    },
  • MCP dispatch handler for the tool, validates args and delegates to ZetrixSDK.isAccountActivated.
    case "zetrix_sdk_is_activated": {
      if (!args) {
        throw new Error("Missing arguments");
      }
      const isActivated = await zetrixSDK.isAccountActivated(args.address as string);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({ address: args.address, isActivated }, null, 2),
          },
        ],
      };
    }
  • Core implementation: Calls official Zetrix SDK's account.isActivated, handles errorCode 4 as inactive account.
    async isAccountActivated(address: string): Promise<boolean> {
      await this.initSDK();
    
      try {
        const result = await this.sdk.account.isActivated(address);
    
        if (result.errorCode !== 0) {
          // If error code is "account not exist", return false
          if (result.errorCode === 4) {
            return false;
          }
          throw new Error(result.errorDesc || `SDK Error: ${result.errorCode}`);
        }
    
        return result.result.isActivated;
      } catch (error) {
        throw new Error(
          `Failed to check account: ${error instanceof Error ? error.message : String(error)}`
        );
      }
    }
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 checks activation status but does not disclose behavioral traits like whether it's a read-only operation, potential rate limits, error conditions, or what 'activated' means in this context. This leaves significant gaps for an AI agent.

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 directly states the tool's purpose without unnecessary details. It is front-loaded and appropriately sized for a simple check operation.

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, no output schema, and a simple input schema, the description is incomplete. It lacks details on what 'activated' entails, the return format, error handling, or how it differs from sibling tools. For a blockchain context with multiple account-related tools, more context is needed.

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%, with the parameter 'address' documented as 'The Zetrix account address.' The description does not add meaning beyond this, such as address format or validation rules. With high schema coverage, the baseline score of 3 is appropriate.

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 tool's purpose: 'Check if an account is activated on the blockchain.' It specifies the verb ('check') and resource ('account'), but does not differentiate from siblings like 'zetrix_get_account' or 'zetrix_get_account_base' which might provide overlapping information about account status.

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. With siblings such as 'zetrix_get_account' and 'zetrix_get_account_assets' that might include activation status, the description lacks explicit context or exclusions for tool selection.

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