Crypto, web, finance and app data tools

Calldata Decoder

decode_calldata

Decode EVM transaction input data: looks up the 4-byte function selector and decodes every argument (addresses, amounts, arrays). Use to see what a transaction or signing request will really do.

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

Input Schema

Name	Required	Description	Default
`data`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It conveys the decoding behavior and output contents (arguments decoded), which is useful, but does not mention error handling for unknown selectors, permission requirements, or whether output is purely informational. Adequate but leaves gaps for an annotation-free tool.

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?

Two efficient clauses, front-loaded with the core action and followed by the practical use case. No wasted words.

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 an output schema present, the description needn't explain return values; it only needs to make the input and purpose clear. For a single-parameter decode tool it is nearly complete, missing only calldata format details.

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 coverage is 0% and the single parameter "data" is undocumented in the schema. The description implies data is EVM transaction input/calldata, partially compensating, but does not specify format (hex string, 0x prefix, selector-only vs full calldata).

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 (decode) and resource (EVM transaction input data), then explains the mechanics (4-byte selector lookup, decoding of addresses, amounts, arrays). This clearly identifies what the tool does, though it does not explicitly differentiate it from siblings like read_contract or contract_info.

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?

"Use to see what a transaction or signing request will really do" gives a clear trigger context. It lacks explicit when-not guidance or named alternatives, but the intended usage scenario is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?