Skip to main content
Glama

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

NFT balance, Arbitrum

arb_nft_balance
Read-only

How many NFTs of one ERC-721 collection a wallet holds on Arbitrum One (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 arb_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": "arb_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
Behavior5/5

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

Goes well beyond the annotations: 422 semantics for missing/non-ERC-721 contracts, the pricing model ($0.01/call via x402 USDC or card key, first 25 free, failed calls free), and the key non-obvious trait that every successful call is charged so repeats are not free — which explains the idempotentHint=false annotation in practical terms. It also reaffirms the read-only nature with 'reads or computes only and changes nothing', consistent with readOnlyHint=true.

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 core operation and the sibling differentiation before pricing and error details, and no sentence is filler. A couple of clauses are redundant with annotations ('reads or computes only and changes nothing' against readOnlyHint=true) and the single dense paragraph could be split for scannability.

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 states what the result includes (balance plus collection name and symbol), and it covers the error case, cost, and read-only nature. For a two-parameter read on a simple balance lookup, nothing an agent needs in order to call it correctly is missing.

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% and the schema already labels both fields as 0x wallet and 0x ERC-721 contract addresses. The description restates the 0x-address constraint and adds the ERC-721 validity requirement, but contributes little semantic detail beyond the schema's own field descriptions, 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 the exact operation (balanceOf for one ERC-721 collection held by a wallet on Arbitrum One) and what comes back (collection name and symbol). It also explicitly separates itself from arb_nft_owner, which answers who holds a specific token id, so an agent can route between the two without opening either 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 two concrete when-to-use cases (pre-token-gate holder check, verifying a wallet still holds a collection) and names the sibling to use when the question is about a specific token id. It also states the failure condition (non-ERC-721 or missing contract returns 422 uncharged), which tells the agent what to expect rather than infer.

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.