Skip to main content
Glama
Sign In
Base MCP Server

Base MCP Server

by khlndaaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

check_token_approvals

Check a wallet's active ERC-20 and NFT approvals on Base, verifying current on-chain state and flagging unlimited allowances as high-risk.

Instructions

Check a wallet's active ERC-20 and NFT token approvals on Base.

Scans historical Approval/ApprovalForAll events, then verifies the CURRENT on-chain state of each unique pair found (an old event doesn't mean the approval is still active — it may have been reduced or revoked since). Flags unlimited approvals as high-risk. This tool is READ-ONLY and cannot revoke anything.

Args: address: The 0x-prefixed wallet address to check.

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": {
      "address": "<address>"
    },
    "name": "check_token_approvals"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Description details the process (scanning events, verifying current state), warns about old events possibly being outdated, and flags unlimited approvals as high-risk. It also clarifies read-only nature. No annotations provided, but description fully covers behavioral traits.

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?

Description is concise with no wasted words: a short intro, a paragraph on behavior, a note on read-only, and clear Args section. Front-loaded purpose.

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?

Given the tool's simplicity (one parameter, no output schema needed due to its existence), description covers purpose, behavior, limitations, and risk flags. No gaps identified.

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 0%, but description adds meaning for the only parameter: 'The 0x-prefixed wallet address to check.' This compensates for the lack of schema description.

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?

Description clearly states the tool checks a wallet's active ERC-20 and NFT token approvals on Base, using a specific verb and resource. It distinguishes from sibling tools like check_rugpull_risk or get_wallet_balance.

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?

Description explains the tool scans historical events and verifies current state, and explicitly states it is read-only and cannot revoke. While it doesn't give explicit when-to-use vs. siblings, the context implies its specific use case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools