Skip to main content
Glama

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

Polygon NFT owner

polygon_nft_owner
Read-only

Owner of an NFT on Polygon PoS: 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 polygon_nft_balance, for the token's metadata polygon_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": "polygon_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?

Annotations already declare readOnly, non-destructive, open-world, and non-idempotent behavior. The description adds important context beyond annotations: 422 responses are uncharged, calls cost $0.01 via x402 USDC or a card key with 25 free, failed calls are free, and repeats are charged because each call is billed. This is rich behavioral disclosure for a paid read tool.

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 description is front-loaded with the core purpose and then layers usage, alternatives, error behavior, an example, pricing, and safety. Every sentence is relevant, though the pricing and charging details make the paragraph dense. It remains readable and well organized.

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 explains the return contents (owner wallet plus collection name and symbol), error semantics, pricing, and safety profile. This is complete enough for an agent to call the tool correctly and interpret likely outcomes.

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 already carry descriptions. The description adds only an example address and tokenId value, which slightly illustrates format but does not add substantive meaning beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource: returns the current owner wallet of one ERC-721 token id on Polygon PoS (ownerOf), plus collection name and symbol. It explicitly separates itself from polygon_nft_balance and polygon_nft_metadata, 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 Guidelines5/5

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

Gives concrete when-to-use scenarios (verifying holder before a trade, mint gate, or airdrop) and names the alternatives for related questions: polygon_nft_balance for counts and polygon_nft_metadata for token metadata. The 422 behavior for missing contracts or nonexistent tokens is also stated.

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.