Skip to main content
Glama

Evm allowance

evm_allowance
Read-onlyIdempotent

ERC20 allowance across 8 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Arc and Robinhood): how much a spender may move from an owner, and whether it is unlimited. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": "evm_allowance"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoethereum (default), base, arbitrum, optimism, polygon, bnb, arc or robinhood
ownerYeswallet that approved (0x...)
tokenYesERC20 contract (0x...)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
spenderYescontract allowed to spend (0x...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chain / description
      Previous value: -"ethereum (default), base, arc or bnb"New value: +"ethereum (default), base, arbitrum, optimism, polygon, bnb, arc or robinhood"
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses significant behavior: the tool costs $0.001 per call, supports x402 payment in USDC on Arc/Base/Solana or XNT on X1, and requires a two-step sign-then-pay handshake. This adds important cost and authentication context that the readOnly/openWorld/idempotent annotations do not convey.

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 description is compact and front-loads the core purpose before explaining the payment flow. The parenthetical list of eight chains is somewhat dense, but every part of the description contributes information an agent needs before calling the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, multi-chain, paid tool with no output schema, the definition covers chains, cost, payment steps, and the semantic meaning of the allowance result. It could go slightly further by describing the exact response shape or common failure modes, but it is otherwise complete enough to call correctly.

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 description coverage is 100%, so the schema already documents all five parameters. The description adds useful conceptual meaning for `owner` and `spender` by explaining that the tool reports how much the spender may move and whether the allowance is unlimited, though it leaves address formatting and chain naming to 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?

The description names a specific resource and operation: ERC20 allowance across eight named EVM chains, clarifying that it reports how much a spender may move from an owner and whether the allowance is unlimited. This clearly distinguishes it from balance-oriented siblings such as evm_token_balance or evm_balances_bulk.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives concrete usage guidance for the paid flow: call once without `payment` to get terms, sign with your own wallet, then call again with `payment`. It does not explicitly name alternatives or exclusions, but the x402 call sequence is clear enough for an agent to use it correctly.

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.

Resources