xportalx

zora_wallet

Get comprehensive Zora NFT wallet data: NFTs minted, NFTs owned, creator profile, total mints/collections, and estimated earnings. FREE - no payment required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "zora_wallet"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	Chain to query (e.g., 'zora', 'base', 'ethereum')	zora
`address`	Yes	Wallet address (EOA or contract) to look up

Schema Changelog

Changes observed during successful MCP inspections.

First observedJan 31, 2026

TDQS

A3.7/5.0

Behavior3/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 does disclose that the tool is FREE and lists the returned data types, which add some context beyond the schema. However, it does not mention whether it is a read-only operation, any rate limits, or what 'comprehensive' means in terms of data coverage. Thus, it provides moderate transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence of about 26 words that front-loads the core action and data types. However, the phrase 'FREE - no payment required' is redundant, as 'FREE' alone implies no payment, so it is not perfectly 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?

For a read-only tool with two well-documented parameters and no output schema, the description provides a clear list of the returned data (NFTs minted, owned, creator profile, total mints/collections, estimated earnings). It lacks explicit mention of output format or corner cases, but it is sufficient for most use cases. The lack of annotations and output schema is offset by the clear purpose and data list.

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%, so the schema already describes 'chain' and 'address' parameters. The description does not add any additional parameter semantics or examples, so it scores at the baseline 3.

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?

The description clearly states 'Get comprehensive Zora NFT wallet data' with a specific resource (Zora NFT wallets) and lists concrete data points (NFTs minted, NFTs owned, creator profile, total mints/collections, estimated earnings). This distinguishes it from sibling tools like nansen_wallet_profiler or get_wallet_balance, which are for other platforms or generic balances.

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 for Zora-specific NFT wallet data but does not explicitly say when to use this tool over alternatives or exclude other tools. There is no mention of conditions like 'use this when you need Zora data' or 'not for general wallet balance checks,' so it relies on implied context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All xportalx tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?