Skip to main content
Glama

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

Arbitrum NFT owner

arb_nft_owner
Read-only

Owner of an NFT on Arbitrum One: 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 arb_nft_balance, for the token's metadata arb_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": "arb_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.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the 422 failure mode for a missing contract or nonexistent token and that such calls are uncharged, states pricing ($0.01/call via x402 USDC or card key, first 25 free, failures free), and warns that each call is charged so repeats are not free — which also explains why idempotentHint=false despite a pure read.

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-loads the purpose, then usage, then error/pricing behavior; almost every clause earns its place. Slight redundancy in the pricing tail ('first 25 free; failed calls free' followed by 'each call is charged, so repeats are not free') costs it a point.

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 specifies what comes back (owner address plus collection name and symbol), plus failure behavior and cost. For a two-parameter read tool, an agent has everything needed to call it correctly and interpret the result.

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 coverage is 100%, so both parameters are already documented; the description only reinforces that tokenId is a single ERC-721 token id and supplies one concrete example pair. That is mildly useful for address/token formats but adds little meaning beyond the schema, matching the baseline of 3.

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?

States a specific verb+resource pair ('Owner of an NFT on Arbitrum One') and names the underlying call (ownerOf), plus the extra data returned (collection name and symbol). It explicitly contrasts with arb_nft_balance and arb_nft_metadata, so an agent can pick it apart from siblings 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?

Gives concrete use cases (verifying holder before a trade, mint gate, airdrop) and names two alternative tools with the exact condition that should route to them (count held vs. token metadata). Nothing about tool selection 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.