Skip to main content
Glama

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

Token allowance, Ethereum ERC-20

eth_allowance
Read-only

ERC-20 token allowance on Ethereum: 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 eth_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": "eth_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.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds real behavior beyond them: 422 errors for a missing/non-ERC-20 contract, the fact that failed calls are free, and pricing ($0.01/call, first 25 free). It also explains the non-idempotent annotation in billing terms ('each call is charged, so repeats are not free'), which an agent cannot infer from the hint alone.

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 purpose, then return shape, then alternatives, then error/cost notes – a sensible ordering with no filler. It runs long as a single dense paragraph, and the pricing tail could be split out for scanability, but every clause carries information an agent needs.

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 three required params, no output schema, and no enums, the description supplies exactly what is missing: the return fields (raw, token units, unlimited flag), failure mode, and cost model. Nothing an agent needs to call it correctly is absent.

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 the baseline is 3. The description adds meaning on top: the token parameter accepts a ticker OR a 0x contract, and an invalid/non-ERC-20 contract yields a 422 that is not charged – semantics absent from 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?

States a specific verb+resource (ERC-20 allowance on Ethereum) and enumerates what is returned: raw allowance, token-unit allowance, and an unlimited-approval flag. It explicitly distinguishes itself from the balance sibling (eth_token_balance), so an agent can choose it 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?

Names two concrete use cases (pre-swap approval check, auditing risky open approvals) and routes the balance question to eth_token_balance. The 'Ethereum' scoping plus the per-chain allowance siblings also makes the chain-selection condition clear.

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.