Skip to main content
Glama

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

Base NFT owner

base_nft_owner
Read-only

Owner of an NFT on Base: 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 base_nft_balance, for the token's metadata base_nft_metadata. A missing contract or a token that does not exist is 422, uncharged. Example: contract=0x03a520b32C04BF3bEEf7BEb72E919cf822Ed34f1, 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": "base_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.8/5.0
Behavior5/5

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

Beyond the readOnlyHint/destructiveHint annotations, it discloses the error contract (missing contract or nonexistent token = 422, uncharged), the pricing model ($0.01/call via x402 USDC or card key, first 25 free, failed calls free), and that repeats are re-charged — which explains why idempotentHint is false. 'Reads or computes only and changes nothing' reinforces rather than contradicts the annotations.

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 what the tool returns, then alternatives, then failure modes and pricing — the ordering matches how an agent needs the information. It is a dense single paragraph and the pricing sentences are long, but each carries distinct decision-relevant content rather than 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, yet the description names all three returned pieces (owner address, collection name, symbol), states the failure behavior, and covers cost. For a two-parameter read tool that is everything an agent needs before calling.

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 already 100%, so the schema carries the baseline; the description adds marginal value by naming the ERC-721/ownerOf semantics of the pair and supplying a concrete worked example (contract=0x03a5..., tokenId=1) that demonstrates the expected address and id format. It does not add constraints such as accepted tokenId ranges or address checksums, so it is an improvement on the baseline rather than a full compensation.

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 ('Owner of an NFT on Base ... the wallet that holds one ERC-721 token id right now (ownerOf), plus the collection's name and symbol'), and explicitly names the sibling tools base_nft_balance and base_nft_metadata as the alternatives for adjacent questions. An agent can distinguish this from the balance and metadata tools without opening any 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 triggers ('verify who holds an NFT before a trade, a mint gate or an airdrop') and explicitly routes the count question to base_nft_balance and the metadata question to base_nft_metadata. The alternatives and selecting conditions are stated, not inferred.

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.