Skip to main content
Glama

approval-check

Check a token approval before signing it: reads the ERC-20 allowance (owner -> spender) live on Base and returns the raw allowance, an unlimited-approval flag and a risk verdict. Read-only, no keys, no transaction.

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": {
      "owner": "<owner>",
      "spender": "<spender>"
    },
    "name": "approval-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYesERC-20 token owner address (0x + 40 hex).
tokenNoERC-20 token address. Defaults to USDC on Base.
spenderYesSpender address whose allowance is checked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose key behavior: it reads live on Base, requires no keys, submits no transaction, and returns the raw allowance plus an unlimited-approval flag and risk verdict. It still leaves out failure modes, rate limits, and the exact risk-verdict semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single efficient sentence with the primary action front-loaded, followed by scope, return details, and safety traits. Every clause earns its place.

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?

There is no output schema, but the description names the return contents (raw allowance, unlimited-approval flag, risk verdict) and clarifies the read-only nature. It is nearly complete, though it could say more about what the risk verdict represents.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents owner, token, and spender, including the token default. The description only restates the owner-to-spender relationship and adds no meaningful syntax or formatting guidance beyond 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 states a specific verb ('Check'), a specific resource ('token approval' / 'ERC-20 allowance'), and the exact scope ('owner -> spender') on Base. It is clearly distinguishable from sibling preflight/check tools because it is about ERC-20 allowance risk before signing.

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 phrase 'before signing it' gives a clear usage context, and 'Read-only, no keys, no transaction' reinforces when this is appropriate. However, it does not name exclusions, alternatives, or conditions where another sibling tool should be used instead.

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