Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Ethereum NFT owner

eth_nft_owner
Read-only

Owner of an NFT on Ethereum: the wallet that holds one ERC-721 token id right now (ownerOf), plus the collection's name and symbol. Use to verify who holds an NFT before a trade, a mint gate or an airdrop; for how many a wallet holds use eth_nft_balance, for the token's metadata eth_nft_metadata. A missing contract or a token that does not exist is 422, uncharged. Example: contract=0xC36442b4a4522E871399CD717aBDD847Ab11FE88, tokenId=1. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": "eth_nft_owner"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenIdYesToken id, a whole number
contractYes0x ERC-721 collection contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, and the description reinforces this with 'Reads or computes only and changes nothing.' It adds real value beyond the annotation block: 422 on a missing contract or nonexistent token and uncharged failures, plus cost/payment mechanics ($0.01/call via x402 USDC or card key, first 25 free). It does not explain the idempotentHint=false nuance (owner can change between calls), which keeps it from a 5.

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 definition is front-loaded: purpose and return values first, then use cases and alternatives, then error/pricing details. It is dense and the payment/credits sentence is long, but each sentence carries operational information rather than filler.

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?

With no output schema, the description still tells the agent what comes back (holder wallet plus collection name and symbol) and how failures behave (422, uncharged). For a two-parameter read tool this covers everything needed to call and interpret it correctly.

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 both parameters are already documented as a 0x ERC-721 contract address and a whole-number token id. The worked example with a concrete contract address and tokenId=1 adds marginal concreteness but no new meaning beyond the schema, so 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?

The description states a specific resource and operation: the current holder of one ERC-721 token id (ownerOf), plus collection name and symbol. It explicitly distinguishes itself from eth_nft_balance (counts) and eth_nft_metadata (metadata), so an agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

It names concrete when-to-use scenarios (verify a holder before a trade, mint gate, airdrop) and explicitly names the alternatives with the condition that selects them ('for how many a wallet holds use eth_nft_balance, for the token's metadata eth_nft_metadata'). Nothing is left to inference.

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.