Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Decode calldata: function and arguments of an EVM call

evm_decode_calldata
Read-only

Decode EVM transaction calldata into the function and its arguments with viem: give the function signature (transfer(address,uint256)), or leave it out to try common ERC-20, ERC-721, ERC-1155, WETH, permit and multicall functions by selector. Numbers come back as decimal strings. Use to read what a pending or past transaction does before signing; get calldata from eth_tx. A selector that does not match is 422, uncharged. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
dataYes0x calldata (selector plus ABI-encoded arguments), up to 8 KB
signatureNoOptional function signature such as transfer(address,uint256)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses output formatting (decimal strings), failure behavior (422 for unmatched selector, uncharged), pricing and free-call rules, and that repeated calls are charged. These details are consistent with readOnlyHint=true, destructiveHint=false, and idempotentHint=false.

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 and primary usage are front-loaded, followed by decoding details, error behavior, and cost. It is dense but mostly earns its space; the final read-only/charging sentence slightly repeats annotation and billing ideas already covered.

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?

For a two-parameter decoding tool with no output schema, the description covers input interpretation, fallback decoding behavior, output format, failure mode, cost, and safety. An agent has enough information to invoke it correctly without needing return-value details from an output schema.

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 already 100%, so the baseline is 3. The description adds useful meaning beyond the schema by explaining that the optional signature may be omitted to try common ERC-20, ERC-721, ERC-1155, WETH, permit, and multicall selectors, and that calldata can come from eth_tx.

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

Purpose5/5

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

The description states a specific verb and resource: decoding EVM transaction calldata into the called function and its arguments. It distinguishes the operation from transaction retrieval by naming eth_tx as the calldata source and explains selector-based fallback decoding.

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

Usage Guidelines4/5

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

It gives clear usage context: use it to inspect what a pending or past transaction does before signing, and obtain calldata from eth_tx. It also explains when to provide a signature versus omit it, though it does not explicitly exclude or compare against any alternative decode tool.

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.