Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

agent_execution_firewall

[$0.10] Decode EVM transaction calldata, detect infinite ERC-20 approvals or permit drainers, run dry-run eth_call simulation, and check 48h exploit feeds before signing.

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": "agent_execution_firewall"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTarget contract or recipient EVM address (0x...)
dataNoHex calldata payload (e.g. '0x095ea7b3...')0x
chainNoTarget chain ('base' or 'ethereum')base
from_addrNoOptional sender address for eth_call dry-run0x0000000000000000000000000000000000000001
value_weiNoOptional native value in wei (decimal string)0
timeout_msNoOptional deadline in ms. If the local LLM would exceed it, the response comes back fast with "degraded": true and non-LLM/cached data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does convey meaningful behavioral traits: a $0.10 cost, that analysis is a non-destructive dry run ('before signing' implies no transaction is submitted), and the existence of cached exploit feeds. It does not state side-effect freedom explicitly, nor what the verdict output looks like (risk flag? boolean?), leaving an agent to guess at the response shape.

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 sentence, front-loaded with the price and then the four capabilities in execution order. Every clause maps to a real function of the tool, with no filler. It reads as a dense run-on feature list, which slightly hurts scannability, but nothing is wasted.

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

Completeness3/5

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

For a six-parameter analysis tool with no annotations and no output schema, the description covers inputs and intent but leaves the return value entirely unexplained — an agent cannot tell whether it receives a risk score, a decoded call summary, or a boolean verdict. It is adequate to decide to call it but incomplete for interpreting the result.

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 all six parameters (to, data, chain, from_addr, value_wei, timeout_ms) are already documented in the schema, and the description adds no parameter-specific meaning beyond what is there. Per the rubric, a 3 is the correct baseline when the schema does the heavy lifting.

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 pairs specific verbs with concrete resources: decode calldata, detect infinite ERC-20 approvals / permit drainers, run eth_call simulation, check 48h exploit feeds. This is far more than a restatement of the name and lets an agent infer it is an EVM transaction risk analyzer. It does not explicitly distinguish itself from plausible siblings such as agent_preflight or security_preflight_402, so it falls short of 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 Guidelines3/5

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

The trailing phrase 'before signing' implies the correct moment to call it, which is useful context. However, there is no explicit when-not guidance, no prerequisites (e.g. required chain support), and no named alternative for agents deciding between this and other preflight/security tools. Usage is implied rather than stated.

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