Skip to main content
Glama
quackai-org

@quackai/q402-mcp

Official
by quackai-org
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

q402_clear_delegation

Clear the EIP-7702 delegation on a selected Q402 chain to reset it or switch your wallet to the x402 rail on Base, using two-phase consent and a prior status check.

Instructions

Clear the EIP-7702 delegation on a Q402 chain for the configured wallet. Call this when the user wants to reset a chain's delegation, OR to switch a wallet off the q402 rail so it can use the x402 (EIP-3009) rail on Base (a q402-delegated wallet can't settle x402). The next q402_pay on the same chain re-creates the delegation automatically, so don't clear right before a normal pay. Pair with q402_wallet_status / q402_agentic_info first to see which chains have an active delegation. Works in all three wallet modes: eoa (Q402_PRIVATE_KEY) and agentic-local (Q402_AGENTIC_PRIVATE_KEY) sign LOCALLY; agentic-server (Mode C) holds only a live apiKey and the server signs with the encrypted Agent Wallet key. Q402 sponsors the on-chain TX on every chain EXCEPT Ethereum, where the gas is billed to your Gas Tank. Two-phase consent: call once WITHOUT consentToken to get a preview + token (no broadcast), then re-call with the same args plus that consentToken to execute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYesWhich Q402 chain to clear the delegation on.
walletIdNoServer-managed Agent Wallet only (walletMode="agentic-server"). Lowercased Agent Wallet address when you hold more than one; omit to use your single/default wallet.
walletModeNoWhich wallet to clear. "eoa" = Q402_PRIVATE_KEY, "agentic-local" = Q402_AGENTIC_PRIVATE_KEY (both sign locally), "agentic-server" = server-managed Agent Wallet (apiKey only, no private key). Omit when only one mode is configured; required when several are.
consentTokenNoTwo-phase consent. Omit on the first call to get a needs_confirmation preview + consentToken (no broadcast); re-call with the SAME args plus this token to execute. Re-derived from the resolved chain + wallet.

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and exceeds it: it discloses the two-phase consent flow (preview + token, then execute), wallet-mode signing differences, gas sponsorship per chain, and automatic delegation re-creation on next q402_pay.

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 dense yet front-loaded: first sentence states purpose, subsequent sentences cover usage, exclusions, wallet modes, gas, and consent flow. No sentence is wasted.

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?

The tool is complex (two-phase consent, multiple wallet modes, chain-specific gas), and the description fully explains all mechanics despite no output schema. It is complete and self-sufficient.

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%, providing baseline 3. The description adds operational meaning beyond the schema, such as how walletMode relates to signing locations and the consentToken re-derivation from chain+wallet.

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 starts with a specific verb+resource: 'Clear the EIP-7702 delegation on a Q402 chain for the configured wallet.' It clearly distinguishes from siblings by naming q402_pay, q402_wallet_status, and q402_agentic_info as related but different operations.

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?

The description explicitly states when to call ('reset a chain's delegation, OR to switch a wallet off the q402 rail so it can use the x402 rail'), when not to ('don't clear right before a normal pay'), and which tools to pair with first (q402_wallet_status / q402_agentic_info).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/quackai-org/q402-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server