Skip to main content
Glama

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

Token allowance, Polygon ERC-20

polygon_allowance
Read-only

ERC-20 token allowance on Polygon PoS: how much a spender may move from an owner's wallet (allowance), raw and in token units, and whether the approval is unlimited. Use to check an approval before a swap or to audit risky open approvals; for the owner's balance use polygon_token_balance. Token is a ticker (USDC, USDT, WETH…) or a 0x contract; a missing contract or a non-ERC-20 one 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": {
      "token": "<token>",
      "owner": "<owner>",
      "spender": "<spender>"
    },
    "name": "polygon_allowance"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYes0x wallet that gave the approval
tokenYesToken: a ticker such as USDC or WETH, or the 0x ERC-20 contract address
spenderYes0x contract or wallet allowed to spend (the example is Uniswap Permit2)

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?

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this ('reads or computes only and changes nothing'). It goes further than annotations by disclosing cost ($0.01/call via x402 or card key, first 25 free, failed calls free), the 422-unmetered failure mode, and why repeats aren't free — which reconciles the idempotentHint=false on an otherwise read-only call.

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 definition, then usage, then failure/cost semantics — a logical order with no filler. The pricing and free-tier clauses are somewhat long but are operationally relevant, so they earn most of their place.

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 still characterizes the return values (allowance raw and in token units, unlimited flag). Combined with failure-mode and cost disclosure, an agent has everything needed to call it correctly and interpret the result.

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 all three params are already documented. The description still adds meaning: it clarifies that token accepts either a ticker (USDC, USDT, WETH) or a 0x contract, and that a missing or non-ERC-20 contract yields a 422 rather than a null result.

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 — 'ERC-20 token allowance on Polygon PoS' — and immediately defines the returned quantity (raw and in token units, plus unlimited-approval flag). It explicitly distinguishes itself from the balance sibling: 'for the owner's balance use polygon_token_balance.'

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 an approval before a swap or to audit risky open approvals') and names the alternative tool to use for a different need (polygon_token_balance). The routing decision is fully determined without inspecting either schema.

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.