Skip to main content
Glama

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

Token allowance, Optimism ERC-20

op_allowance
Read-only

ERC-20 token allowance on Optimism: 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 op_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": "op_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 cover readOnly/destructive/openWorld, but the description adds real context the annotations don't: cost ($0.01/call via x402 or card key), first 25 free, failed calls free, and that repeat calls are not free because each is charged. That also explains the seemingly odd idempotentHint=false, so there is no contradiction. It stops short of describing the response shape beyond field names, which is acceptable given no output schema.

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?

The purpose and return semantics are front-loaded, followed by usage, then pricing/error details. It is dense but each clause carries information an agent needs for a charged call; the pricing sentence is slightly crammed into an otherwise tight paragraph.

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 tells the agent what comes back (raw and token-unit allowance plus an unlimited-approval flag). Combined with cost and error behavior, nothing essential is missing for a 3-required-parameter read-only tool.

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 earns a bump by explaining token resolution (ticker such as USDC/WETH OR 0x contract) and the resulting 422 failure mode, plus framing owner as the approver and spender as the approved party. No enum or format details beyond that are added.

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 token allowance on Optimism' with what is returned (raw and token units, unlimited flag). It explicitly contrasts with the sibling 'op_token_balance', so the agent can distinguish allowance from balance 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?

Gives concrete when-to-use cases ('check an approval before a swap', 'audit risky open approvals') and names the alternative tool for owner balance. It also states a when-not/edge case: a missing contract or non-ERC-20 token yields 422 and is uncharged.

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.