Skip to main content
Glama

APEX DeFi, DefiLlama & 8-Chain EVM Intel

Evm log decode

evm_log_decode
Read-onlyIdempotent

Decode all EVM transaction event logs (ERC-20/721/1155, Uniswap V2/V3 swaps, approvals, CCTP, EIP-3009) + net asset flows, OR preflight-simulate unsigned calldata across 8 EVM chains (ethereum, base, arbitrum, optimism, polygon, bsc, arc, robinhood). $0.004 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "chain": "<chain>"
    },
    "name": "evm_log_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNosimulation mode: target address (0x...)
txNotx hash (0x + 64 hex) to decode mined logs
dataNosimulation mode: 0x hex calldata
fromNosimulation mode: optional caller
chainYesethereum, base, arbitrum, optimism, polygon, bsc, arc or robinhood
valueNosimulation mode: native wei
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: a per-call price of $0.004, an x402 payment requirement with accepted assets/chains, and the two-step terms-then-payment handshake. It omits what a failed payment or malformed calldata returns, which keeps it below a 5.

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?

Front-loads the two capabilities, then the chain list, then price, then the payment procedure — each sentence carries distinct information with no filler. The dense parenthetical standards list is justified because it tells the agent which log types are covered.

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

Completeness4/5

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

With no output schema and seven parameters, the description covers mode selection, chain coverage, cost, and the payment protocol, which is most of what an agent needs before calling. Remaining gaps are the response shape and precedence rules when mode-determining parameters conflict.

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%, so the baseline is 3; the description earns an increment by explaining the `payment` handshake (pass the signed base64 payload and the purchase completes in-call) and by framing the to/data/value/from cluster as simulation-mode inputs versus tx as decode-mode input. It still does not say what happens if both `tx` and `to` are supplied.

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 specific verbs and resources: decode EVM transaction event logs across named token/swap standards (ERC-20/721/1155, Uniswap V2/V3, CCTP, EIP-3009) and, alternatively, preflight-simulate unsigned calldata. The dual-mode scope is clear and supported chains are enumerated. It does not name the adjacent siblings (calldata_decode, evm_tx) it overlaps with, so differentiation is inferred rather than stated.

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?

Gives a concrete operational sequence for payment ('call once without `payment` for the terms, sign them, call again with `payment`'), which is real usage guidance. However, it never explains when to pick this tool over calldata_decode or evm_tx, nor which inputs select which mode; the mode mapping is left to the schema's per-field 'simulation mode:' prefixes.

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.