Skip to main content
Glama

get_account

Get account information from Bloomfilter: wallet address, domain count, and total spent.

Instructions

Get account information — wallet address, domain count, total spent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The getAccount function that executes the tool logic. It authenticates, calls GET /account, and formats the response.
    export async function getAccount(client: BloomfilterClient): Promise<McpToolResult> {
      const keyError = client.requiresPrivateKey();
      if (keyError) return keyError;
    
      try {
        await client.ensureAuth();
    
        const { data } = await client.http.get<AccountResponse>("/account", {
          headers: client.getAuthHeaders(),
        });
    
        const text = [
          "Account Information:",
          `  Wallet: ${data.wallet_address}`,
          `  Domains: ${data.domains_registered}`,
          `  Total Spent: $${(data.total_spent_cents / 100).toFixed(2)}`,
          `  Member Since: ${data.created_at}`,
          `  Last Active: ${data.last_active_at}`,
        ].join("\n");
    
        return { content: [{ type: "text", text }] };
      } catch (error) {
        return formatToolError(error);
      }
    }
  • AccountResponse interface defining the shape of the API response used by get_account.
    export interface AccountResponse {
      wallet_address: string;
      created_at: string;
      total_spent_cents: number;
      domains_registered: number;
      last_active_at: string;
    }
  • src/index.ts:226-231 (registration)
    Registration of the 'get_account' tool with the MCP server, linking the name to the getAccount handler.
    server.tool(
      "get_account",
      "Get account information — wallet address, domain count, total spent.",
      {},
      async () => getAccount(client),
    );
Behavior3/5

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

No annotations provided; description is minimal. It implies a read operation via 'get' but does not disclose authentication, rate limits, or side effects. Adequate for a simple query with no destructive potential.

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?

Single sentence with clear structure, front-loaded verb and resource. Every part is necessary and concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero parameters and no output schema, the description sufficiently outlines the return fields (wallet address, domain count, total spent). Could include error conditions or authentication notes, but for a basic get tool it is adequate.

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?

No parameters (0), so baseline is 4 per rubric. Description adds value by listing the returned fields, which helps the agent understand what information will be provided.

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?

Description clearly states 'Get account information' with specific fields (wallet address, domain count, total spent). It is a specific verb+resource that distinguishes from sibling tools which handle DNS records and domain operations.

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?

Usage is implied: use when needing account-level info. No explicit when-to-use or alternatives given, but sibling tools are different enough that context is clear.

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/BloomFilter-Labs/mcp-server-bloomfilter'

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