Skip to main content
Glama

EVM calldata decoder with pre-signing risk flags

chain_calldata_decode
Read-only

Decodes EVM calldata before signing: function signature, selector, named arguments, candidate signatures for ambiguous selectors, one level of bundled calls (multicall, Multicall3, ERC-4337 execute, Safe execTransaction, multiSend), token symbol and decimals, and risk flags with reasons for unlimited approvals, setApprovalForAll, permits, transferFrom, admin calls and delegatecall. Sources: Sourcify ABIs and 4byte signatures, JSON-RPC via PublicNode. Price: $0.002 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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": {
      "data": "<data>"
    },
    "name": "chain_calldata_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoContract the transaction is sent to. When given, its Sourcify-verified ABI (following a proxy to its implementation) decodes the call, and token symbol, decimals and contract-code checks are added.
dataYesTransaction calldata, 0x-prefixed hex with a 4-byte selector; at most 16,384 hex digits (8 KB).
chainNoChain of the transaction by name or id: base (8453), ethereum (1), arbitrum (42161), optimism (10), polygon (137), avalanche (43114). Default base when to is given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses data sources (Sourcify ABIs, 4byte, JSON-RPC via PublicNode), pricing ($0.002 per successful call, USDC via x402 v2), and the billing exception that failed or non-matching calls are free. It also bounds behavior honestly ('one level of bundled calls'), so an agent knows the recursion limit. This is exactly the kind of context annotations cannot carry.

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?

The purpose is front-loaded in the first clause, followed by a dense but non-redundant enumeration of outputs, then a short second sentence covering sources and billing. Every clause carries information, though the long run-on output list is harder to scan than a structured breakdown would be.

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?

There is no output schema, so the description must convey return content, and it does so field by field (signature, selector, arguments, candidates, nested calls, token metadata, risk flags with reasons). Combined with disclosed sources, pricing, and the one-level nesting limit, an agent has everything needed to call it and interpret results.

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%, with each parameter already documented including the proxy-following behavior of 'to' and the 8 KB calldata limit, so the baseline is 3. The description adds no syntax, format, or defaulting detail beyond what the schema states. The schema does the heavy lifting here.

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 opens with a specific verb+resource ('Decodes EVM calldata before signing') and enumerates the exact outputs: function signature, selector, named arguments, candidate signatures, one level of bundled calls, token symbol/decimals, and risk flags. It is unambiguous what the tool produces. It never names or contrasts a sibling such as tx_decode, so an agent cannot tell from the text alone which decoder to prefer, which keeps it below 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?

'Before signing' implies the use context (pre-transaction safety check), and the risk-flag list signals when the tool is valuable. However, there is no explicit when-not guidance, no statement of prerequisites, and no routing to or away from alternatives like tx_decode or chain_sign_inspect. Usage is inferable 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