Skip to main content
Glama

ChainGuard Web3 & MCP Shield

check_eip7702_delegation

Detect active EIP-7702 EOA delegation hijacks (0xef0100...) on Ethereum, Base, Arbitrum, or Polygon.

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_eip7702_delegation"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
networkNobase

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It never states that the operation is read-only, what 'active' means (threshold, block lag, cache), what happens on an unsupported network, or whether any API key/rate limit applies.

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, and the parenthetical hex prefix is a compact, useful signal. The brevity is efficient rather than padded, though it leaves little room for the missing operational detail.

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?

With no annotations, no output schema, and 0% parameter coverage, the description is the sole source of information and omits return shape, verdict semantics, and parameter formats. For a security-check tool whose result an agent must interpret, this leaves significant gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only indirectly implies the address parameter via 'EOA' and partially documents the network parameter by listing four chains, but it never gives accepted network string values, the default of 'base', or address format expectations (0x-hex, EOA vs contract).

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?

States a specific verb (Detect) and a very specific resource (EIP-7702 EOA delegation hijacks, with the 0xef0100 delegation designator), which makes it immediately distinguishable from siblings like check_solana_token2022 or check_mcp_poisoning. It stops short of explicitly naming alternatives, so it lands just under a 5.

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 when-to-use or when-not-to-use guidance is given, and no prerequisites or alternative tools are mentioned. The only implicit scoping is the list of four supported chains, which does not tell an agent when this tool is the right choice over check_tx_firewall or audit_solidity_or_mcp.

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