Skip to main content
Glama

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

NFT balance, Optimism

op_nft_balance
Read-only

How many NFTs of one ERC-721 collection a wallet holds on Optimism (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 op_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": "op_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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description nonetheless adds real context beyond them: 422-and-uncharged on a missing or non-ERC-721 contract, $0.01/call with the first 25 free, and the note that failed calls are free. It even explains why idempotentHint=false matters in practice ('each call is charged, so repeats are not free'), which is genuine added value rather than restatement.

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?

Purpose and the sibling distinction are front-loaded, and the pricing/error clauses come last where they belong. It is packed into a single dense paragraph that mixes semantics, routing, error codes, and billing, so the topics run together, but no sentence is 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?

There is no output schema, and the description compensates by stating what comes back (the balance plus the collection's name and symbol). With two fully documented params, a clear error mode, and a stated cost model, nothing an agent needs to call this 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 description coverage is 100%, so both parameters are already documented as 0x addresses. The description's 'Both inputs are 0x addresses' and 'contract' being an ERC-721 collection merely restates the schema, adding no format, checksum, or validation nuance. Baseline 3 applies 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?

Names a specific verb and resource ('How many NFTs of one ERC-721 collection a wallet holds on Optimism (balanceOf)') and explicitly scopes the result to a single collection plus its name and symbol. It also names the sibling it is not (op_nft_owner) and the condition that distinguishes them, so an agent can pick between them 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 use cases ('check a holder before a token-gated action', 'see whether a wallet still holds a collection') and an explicit alternative for a different question ('for who holds one token id use op_nft_owner'). Both the when-to-use and the when-to-use-something-else are 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.