Skip to main content
Glama

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

NFT balance, Polygon

polygon_nft_balance
Read-only

How many NFTs of one ERC-721 collection a wallet holds on Polygon PoS (balanceOf), with the collection's name and symbol. Use to check a holder before a token-gated action or to see whether a wallet still holds a collection; for who holds one token id use polygon_nft_owner. Both inputs are 0x addresses; a missing contract or one that is not ERC-721 is 422, uncharged. 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>",
      "address": "<address>"
    },
    "name": "polygon_nft_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes0x wallet address
contractYes0x ERC-721 collection contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, open-world, non-idempotent, but the description adds genuinely new behavior: 422 error semantics for missing/non-ERC-721 contracts, failed calls are uncharged, and per-call pricing including the first 25 free. The note that 'each call is charged, so repeats are not free' usefully explains the non-idempotent hint. Only a fuller account of return shape/pagination is missing.

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 purpose and the sibling routing are front-loaded in the first two clauses, then pricing and failure semantics follow. It is dense and partly duplicated ('failed calls free' / 'each call is charged'), which costs a little efficiency but nothing is irrelevant.

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, yet the description says what comes back (balance plus collection name and symbol), what inputs must look like, what failure returns, and what it costs. For a 2-parameter read tool this is complete enough to invoke 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 real semantics: both inputs are 0x addresses and the contract must be an existing ERC-721 collection or the call returns 422. That constraint meaningfully extends what the schema states.

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 names a specific verb and resource — 'How many NFTs of one ERC-721 collection a wallet holds on Polygon PoS (balanceOf)' — plus the returned fields (collection name and symbol). It explicitly contrasts itself with polygon_nft_owner ('for who holds one token id use polygon_nft_owner'), so an agent can route between the two without opening schemas.

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?

Both the when ('check a holder before a token-gated action', 'see whether a wallet still holds a collection') and the alternative-when ('for who holds one token id use polygon_nft_owner') are stated explicitly. Nothing about 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.