Crypto, web, finance and app data tools

NFT Metadata

nft_metadata

Metadata of an ERC-721 or ERC-1155 token: token URI resolved from IPFS, Arweave, data URI or https into name, description, image link and traits. Use for NFT displays, rarity or appraisal.

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

Name	Required	Default
`chain`	No	ethereum
`contract`	Yes
`token_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that token URIs are resolved across IPFS, Arweave, data URI and https, which is non-obvious behavior, but it says nothing about failure modes (unresolvable URIs, non-standard contracts) or chain coverage limits.

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?

Two tightly written sentences, front-loaded with what the tool returns and followed by the resolution sources and use cases. No filler.

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

Completeness3/5

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

An output schema exists, so return shape needn't be restated, and the description covers resolution sources. However, with zero parameter documentation and no annotations, an agent gets no guidance on what 'contract' should look like, which chains are supported, or what happens on unresolvable metadata.

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%, so the description must explain the three parameters. It mentions none of them — not the contract address, the token_id, or the chain parameter with its default of ethereum. It partially compensates by describing what the resolved output contains, but the parameter gap is real.

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?

Names a specific verb+resource ('Metadata of an ERC-721 or ERC-1155 token') and enumerates what is produced (name, description, image link, traits). This clearly distinguishes it from siblings like nft_owner (ownership) and erc20_token_info (fungible token data).

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?

'Use for NFT displays, rarity or appraisal' gives implied usage context but no explicit when-not conditions or named alternatives. An agent still has to infer that this is not the tool for ownership or contract-level data.

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

All Crypto, web, finance and app data tools 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?