Skip to main content
Glama

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

NFT balance, Base

base_nft_balance
Read-only

How many NFTs of one ERC-721 collection a wallet holds on Base (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 base_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": "base_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.4/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, and notably idempotentHint=false; the description earns credit for disclosing the 422-on-missing-or-non-ERC-721-contract behavior (uncharged), the $0.01/call x402 pricing with 25 free calls and failed calls free, and the returned name/symbol fields. The 'repeats are not free' note is consistent with idempotentHint=false rather than contradicting it. It stops short of describing output shape or batching, but the additions are substantive.

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-loaded with the core operation and sibling routing, then pricing and error semantics. Slightly overpacked: 'Reads or computes only and changes nothing' largely duplicates readOnlyHint, and the pricing clause runs long.

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?

For a two-parameter read with no output schema, the definition covers inputs, failure mode, pricing, and return contents (name and symbol), plus the alternative tool. Nothing an agent needs 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 both parameters already document themselves as 0x wallet and 0x ERC-721 contract addresses. The description restates that both are 0x addresses and adds the ERC-721 validity constraint with its 422 consequence, which is modest value on top of an already complete schema.

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 (count ERC-721 holdings for one collection via balanceOf on Base) and explicitly distinguishes itself from base_nft_owner, which answers 'who holds one token id.' The agent can select 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 use cases (pre-token-gate holder check, re-checking whether a wallet still holds a collection) and names the alternative tool with the condition that selects it. No inference is required.

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.