Skip to main content
Glama

Nft info

nft_info
Read-onlyIdempotent

NFT owner and metadata link for an ERC721 token across 8 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Arc and Robinhood): owner, collection name and symbol, tokenURI. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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>",
      "id": "<id>"
    },
    "name": "nft_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYestoken id
chainNoethereum (default), base, arbitrum, optimism, polygon, bnb, arc or robinhood
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
contractYesERC721 contract (0x...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chain / description
      Previous value: -"ethereum (default), base, arc or bnb"New value: +"ethereum (default), base, arbitrum, optimism, polygon, bnb, arc or robinhood"
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, and the description adds real context beyond them: it is a paid call at $0.001, settled over x402 with specific accepted tokens, executed as a two-step terms-then-payment handshake. It does not disclose error behavior, what happens on an unpaid second call, or whether charges occur on failed lookups, so it stops short of full 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?

Three tight sentences, front-loaded with what is returned and where, followed by pricing and the call protocol. Every sentence carries information; the chain enumeration in prose slightly duplicates the schema's chain description.

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

Completeness5/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 naming the exact returned fields (owner, collection name and symbol, tokenURI). Combined with the supported-chain list and the full payment protocol, an agent has everything needed to invoke this correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: it explains why `payment` exists (two-call terms/sign/pay cycle) and that the payment is signed with the caller's own wallet. The chain list in prose is redundant with the schema, but the payment semantics are genuinely additive.

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 opens with a specific verb+resource: NFT owner, collection name/symbol, and tokenURI for an ERC721 token, plus the exact set of 8 supported chains. That is enough to distinguish it from a generic chain-info tool, but it never explicitly contrasts with the close sibling evm_token_info, leaving the ERC721-vs-fungible distinction implicit.

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 guidance is strong for the payment mechanic: "Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`" gives an unambiguous procedure. However, there is no guidance on when to choose this over evm_token_info or other asset lookups, nor any statement of prerequisites such as a valid contract address or unsupported-chain behavior.

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