Skip to main content
Glama

ERC-721 facts for one token: owner, collection name

evm_nft
Read-only

ERC-721 facts for one token: owner, collection name and symbol, tokenURI, and its metadata (name, description, image) when the URI is http(s) or ipfs. The metadata fetch has a 5-second timeout and a 256 KB cap; a failed fetch is reported in metadataNote and does not fail the call. Related tools on this server, for a different need: evm_token when you need to check an ERC-20 token's facts, proxy, owner and risks; evm_balance when you need ERC-20 balance of an address for one token contract. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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>",
      "tokenId": "<tokenId>"
    },
    "name": "evm_nft"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNobase (default), ethereum, arbitrum, optimism or polygon
tokenIdYesToken id, decimal
contractYesERC-721 contract, 0x…

Output Schema

NameRequiredDescriptionDefault
chainNo
ownerNo
sourceNo
tokenIdNo
contractNo
metadataNo
tokenUriNo
checkedAtNo
collectionNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only say readOnlyHint and openWorldHint; the description adds substantial behavior the annotations cannot convey: a 5-second metadata fetch timeout, a 256 KB cap, and that a failed fetch surfaces in metadataNote rather than failing the call. It also discloses the pricing model ($0.002 per successful call via x402, failures not charged), which is directly decision-relevant for an agent.

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?

Front-loaded with the resource and returned fields, then metadata caveats, then sibling routing, then pricing — a sensible order with no filler. The pricing sentence is long but carries genuinely useful information, so it earns its place.

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?

With an output schema present, return-shape explanation is unnecessary, and the description still covers scope, metadata-fetch failure semantics, and cost. Minor gap: it does not say what happens when tokenURI is neither http(s) nor ipfs (presumably metadata is simply omitted).

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% — chain (with default and allowed values), tokenId (decimal), and contract (0x…) are all documented in the schema itself. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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: ERC-721 facts for one token, and enumerates exactly what is returned (owner, collection name/symbol, tokenURI, metadata). It explicitly distinguishes itself from evm_token (ERC-20) and evm_balance (ERC-20 balances), so an agent can select it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing for the two nearest siblings: evm_token for ERC-20 facts/proxy/owner/risks and evm_balance for ERC-20 balances. It does not state a negative condition for this tool (e.g., non-EVM chains belong to solana_token, or when token_metadata/image would be preferred), so the exclusions are only partially covered.

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