Skip to main content
Glama

EIP-7702 Smart-Wallet, Passkey Session Key & Gas-Optimizer MCP

Build EIP-7702 Type-0x04 Smart-Wallet Upgrade & Passkey Session Delegation

build_eip7702_smart_wallet_and_passkey_delegation
Read-onlyIdempotent

Upgrades any standard EOA wallet in-place via EIP-7702 (Coinbase Smart Wallet, MetaMask Delegator, ERC-7579 Kernel) with RIP-7212 P-256 Passkey & bounded spend caps.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "build_eip7702_smart_wallet_and_passkey_delegation"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainIdNoEVM chain ID (default '8453')
eoaAddressNoUser or agent 0x EOA wallet address
delegatePresetNo'coinbase_smart_wallet', 'metamask_delegator_7702', or 'kernel_erc7579'
dailySpendCapUsdcNoMax daily USDC allowance (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior1/5

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

The description asserts an in-place state-changing upgrade ('Upgrades any standard EOA wallet in-place'), while annotations declare readOnlyHint=true and destructiveHint=false. If the tool only builds unsigned calldata for the user to sign, the description should say so; as written it contradicts the declared safety profile. It also omits what happens to an existing delegation and how the passkey is registered.

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?

A single front-loaded sentence with no filler; each clause (EIP-7702, presets, RIP-7212 passkey, spend caps) carries distinct information. Density of jargon is high but nothing is wasted.

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

Completeness2/5

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

All parameters are optional with defaults and there is no output schema, so the description must explain what is returned (signed transaction? delegation address? auth challenge?) and what the caller must do next. Combined with the unresolved read-only-versus-upgrade tension, the definition leaves an agent unable to predict the effect of calling it.

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 description coverage is 100%, so the schema already documents all four parameters including the delegatePreset values, which the description merely echoes. The phrase 'bounded spend caps' loosely ties to dailySpendCapUsdc but adds no unit, enforcement, or reset semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Upgrades any standard EOA wallet in-place via EIP-7702') and enumerates the supported delegation targets (Coinbase Smart Wallet, MetaMask Delegator, ERC-7579 Kernel) plus passkey and spend-cap features, so an agent can tell what the tool produces. It stops short of differentiating itself from the close sibling build_erc7715_and_coinbase_spend_permission, which also deals with spend permissions.

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

Usage Guidelines2/5

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

No guidance on when to pick this tool over the spend-permission sibling, no prerequisites (chain support for type-0x04, whether the EOA must be undelegated, whether a passkey must already exist), and no exclusions. The agent must infer applicability from the parameter names alone.

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.