Skip to main content
Glama

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

Token allowance, Arbitrum ERC-20

arb_allowance
Read-only

ERC-20 token allowance on Arbitrum One: 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 arb_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": "arb_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?

Beyond the supplied annotations, the description discloses pricing ($0.01/call via x402 or card key), the first-25-free allowance, that failed calls are free, and that the 422 for a missing or non-ERC-20 contract is uncharged. It also explains why idempotentHint=false matters in practice: each call is billed, so repeating is not free. It does not cover pagination-style concerns (none apply) or rate limits, keeping it just short of a 5.

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?

Purpose and return shape are front-loaded, followed by usage routing, input semantics, error/pricing terms, and a safety note. Every sentence carries information, though the payment and free-tier details are slightly dense in a single clause and could be trimmed without loss.

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 explains the return contents (raw and token-unit allowance plus an unlimited flag), the error case, and the cost model. For a three-required-parameter read tool, 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 the baseline is 3, but the description adds real meaning: token accepts either a ticker (USDC, USDT, WETH) or a 0x contract, and a missing or non-ERC-20 contract yields a 422 rather than a result. That is behavioral detail the schema does not convey.

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?

The description opens with a precise verb+resource pair (ERC-20 token allowance) scoped to a specific chain (Arbitrum One), and explains what the value represents (how much a spender may move from an owner's wallet). It explicitly distinguishes itself from the sibling arb_token_balance, so an agent can choose between them without opening a 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?

It states two concrete use cases (pre-swap approval checks and auditing risky open approvals) and names the alternative tool for the adjacent need (owner's balance). When-not guidance is implied by the balance redirection, which is sufficient routing context.

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.