Skip to main content
Glama

Structural EVM Calldata Selector Decoder (Local)

ingravity_decodeEvmCalldataSelector
Read-onlyIdempotent

Decode EVM calldata locally to identify standard 4-byte selectors (ERC-20/721, permit, Permit2, multicall) and extract raw 32-byte ABI words.

Instructions

Structurally parses EVM hexadecimal calldata locally to identify standard 4-byte selectors (ERC-20 approve/transfer/transferFrom, ERC-721 setApprovalForAll, EIP-2612 permit, Permit2, multicall) and extract raw 32-byte ABI words. Pure structural decoding — use ingravity_inspectEvmTransactionFirewall for live risk verdicts and proxy forensics.

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

Input Schema

NameRequiredDescriptionDefault
dataYesHexadecimal EVM calldata string (0x...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real context beyond them: that parsing happens 'locally', that it is 'pure structural' (no verdicts, no network lookups), and which selectors fall inside its recognition scope. It stops short of saying how unrecognized selectors or malformed hex are handled, which is the remaining behavioral gap.

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?

Two sentences, front-loaded with the core action and the supported-selector list, ending with the routing statement. No redundant phrasing and nothing that could be cut without losing information.

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?

For a one-parameter read-only tool with no output schema, the description covers what is parsed and what is extracted (32-byte ABI words), which is enough to invoke it correctly. It could be stronger by sketching the return shape (e.g., matched selector name plus decoded words) and by noting behavior on unmatched calldata, but no critical calling information is missing.

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?

There is a single required parameter (data) with full schema description coverage, so the schema already documents the '0x...' hex format. The description mentions 'EVM hexadecimal calldata' but contributes no additional format, encoding, or length constraints beyond what the schema states. Baseline 3 applies when the schema carries the parameter burden.

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 definition states a specific verb and resource ('Structurally parses EVM hexadecimal calldata') and then enumerates the exact selector families it recognizes (ERC-20 approve/transfer/transferFrom, ERC-721 setApprovalForAll, EIP-2612 permit, Permit2, multicall) plus the raw-word extraction. An agent can tell immediately this is a local structural decoder and not a risk analyzer, and the closing clause places it apart from ingravity_inspectEvmTransactionFirewall.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use frame ('pure structural decoding') and names the alternative with the condition that selects it ('use ingravity_inspectEvmTransactionFirewall for live risk verdicts and proxy forensics'). The boundary between decoding and risk assessment is stated rather than inferred.

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