Skip to main content
Glama

Get profile balances

zora_get_profile_balances

Retrieve coin balances for a wallet or handle on the Zora Coins ecosystem. This tool queries the Base mainnet to list token holdings and profile asset data.

Instructions

List coin balances for a wallet or handle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYes
countNo
afterNo

Implementation Reference

  • Handler function that invokes CoinsSDK.getProfileBalances with provided parameters (identifier, after, count) and returns formatted JSON response.
    async ({ identifier, after, count }) => {
      // @ts-expect-error - TypeScript can't resolve barrel exports properly
      const resp = await CoinsSDK.getProfileBalances({ identifier, after, count });
      return { content: [{ type: "text", text: json(resp) }] };
    }
  • Tool metadata including title, description, and Zod input schema for identifier (string), optional count (1-100), and after (string).
    {
      title: "Get profile balances",
      description: "List coin balances for a wallet or handle.",
      inputSchema: {
        identifier: z.string(),
        count: z.number().int().min(1).max(100).optional(),
        after: z.string().optional(),
      },
    },
  • src/index.ts:248-264 (registration)
    Registers the 'zora_get_profile_balances' tool on the MCP server with schema and handler implementation.
    server.registerTool(
      "zora_get_profile_balances",
      {
        title: "Get profile balances",
        description: "List coin balances for a wallet or handle.",
        inputSchema: {
          identifier: z.string(),
          count: z.number().int().min(1).max(100).optional(),
          after: z.string().optional(),
        },
      },
      async ({ identifier, after, count }) => {
        // @ts-expect-error - TypeScript can't resolve barrel exports properly
        const resp = await CoinsSDK.getProfileBalances({ identifier, after, count });
        return { content: [{ type: "text", text: json(resp) }] };
      }
    );
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 of behavioral disclosure. It mentions 'List coin balances' which implies a read-only operation, but doesn't specify if it's paginated (hinted by 'count' and 'after' parameters), rate-limited, requires authentication, or what the output format looks like. For a tool with three parameters and no output schema, this leaves significant gaps in understanding how it behaves beyond basic functionality.

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 any fluff. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place, and there's no wasted verbiage or redundancy.

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 tool has three parameters with 0% schema coverage, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain the parameters, behavioral details like pagination or error handling, or what the output contains. For a data retrieval tool with multiple inputs, this leaves too much undefined for reliable agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning none of the parameters are documented in the schema. The description only vaguely references 'wallet or handle' which might relate to 'identifier', but doesn't explain what 'identifier' is, what 'count' controls (likely pagination limit), or what 'after' does (likely cursor for pagination). It fails to compensate for the lack of schema documentation, leaving parameters largely unexplained.

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 ('List') and resource ('coin balances for a wallet or handle'), making the purpose understandable. It distinguishes itself from siblings like 'zora_get_profile' or 'zora_get_profile_coins' by focusing specifically on balances rather than general profile data or owned coins. However, it doesn't explicitly differentiate from other balance-related tools if any existed, keeping it at a 4 rather than a 5.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'zora_get_profile' and 'zora_get_profile_coins', there's no indication of when to prefer this tool for balances over those for broader profile data or coin lists. It lacks any context about prerequisites, constraints, or typical use cases, leaving the agent to infer usage based on the name alone.

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/r4topunk/zora-coins-mcp-server'

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