Skip to main content
Glama

zato crypto data

NFT metadata: tokenURI plus the fetched metadata JSON (name, image, attributes) for ERC-721/1155

nft_metadata
Read-only

What an NFT is: tokenURI plus fetched metadata (name, image, attributes) for ERC-721/1155. Price: $0.003 USDC per call (x402, Base).

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": {
      "contract": "<contract>",
      "token_id": "<token_id>"
    },
    "name": "nft_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNo"ethereum" (default) or "base"
contractYesNFT collection contract
token_idYestoken id (decimal)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-fetch behavior are covered structurally. The description adds genuinely useful context the annotations do not: the per-call price of $0.003 USDC via x402 on Base, which is important for an agent deciding whether to spend. It does not disclose failure behavior (unreachable or empty tokenURI, burned or nonexistent token ids) or how metadata is resolved, which limits it to a 3.

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?

Two tight sentences with no filler, and the content statement is front-loaded ahead of the pricing detail. The 'What an NFT is:' framing is slightly awkward as an opening but still communicates the return contents efficiently.

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?

There is no output schema, and the description compensates by enumerating what comes back (tokenURI plus fetched name, image, attributes). Cost and payment rail are also stated. For a three-parameter read tool this is close to complete, with only error and edge-case behavior left unstated.

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 documents network ('ethereum' default or 'base'), contract, and decimal token_id; baseline is 3. The description adds only the ERC-721/1155 token-standard scope, which hints at which contracts are valid but does not elaborate on any parameter beyond the schema.

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 names the concrete resource and verb implicitly: it returns tokenURI plus the fetched metadata JSON (name, image, attributes) for ERC-721/1155 tokens, keyed on a contract and token id. That is specific enough to distinguish it from every listed sibling, which are wallet, risk, and chain-data tools. It loses the top mark only because the phrasing 'What an NFT is:' frames the tool as a definition rather than stating the action directly.

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 gives no when-to-use guidance, no exclusions, and names no alternative tool. An agent must infer usage from the required contract/token_id parameters alone. There is no statement of what this tool is not for (e.g. collection-level stats or ownership checks).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources