Skip to main content
Glama

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

Polygon PoS ERC-20 balance

polygon_token_balance
Read-only

ERC-20 token balance of a wallet on Polygon PoS (USDC, USDT, WETH or any token, via balanceOf): raw amount, decimals, symbol and the human-readable amount, live from the token contract. Use to check stablecoin or token holdings before a transfer or trade; for the native coin use polygon_balance. Both inputs are 0x addresses (40 hex characters); no contract or a non-ERC-20 contract returns 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": {
      "token": "<token>",
      "address": "<address>"
    },
    "name": "polygon_token_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesToken: a ticker such as USDC, USDT, WETH or DAI, or the 0x ERC-20 contract address
addressYes0x wallet 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?

Goes well beyond the annotations by disclosing the return fields (raw amount, decimals, symbol, human-readable amount), the 422 failure mode for non-ERC-20 contracts, and that failures are uncharged. Pricing/free-tier details are useful but partly restated twice ('each call is charged, so repeats are not free' overlaps the price sentence).

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?

Return shape and usage guidance are front-loaded, and the routing hint to polygon_balance comes early. It is dense and mostly earns its length, but the closing clause repeats the read-only annotation and the charge-per-call point already stated in the price sentence.

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?

With no output schema, the description compensates by enumerating the returned fields, and it covers error behavior and cost. Nothing an agent needs to invoke this two-parameter read correctly is missing.

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 baseline is 3; the description still adds a format constraint not in the schema ('Both inputs are 0x addresses, 40 hex characters') and clarifies that the token can be a ticker or any ERC-20 contract. That is real added meaning over the 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?

Names a specific verb and resource ('ERC-20 token balance of a wallet on Polygon PoS'), lists example tokens, and explicitly differentiates from the sibling polygon_balance for the native coin. An agent can pick this tool without opening the 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 an explicit use case ('check stablecoin or token holdings before a transfer or trade') and an explicit exclusion with the alternative named ('for the native coin use polygon_balance'). The when-not case is unambiguous.

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.