Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_crypto_tx_hash_decoder

Decode an EVM transaction by hash to reveal status, fee, method selector, ERC-20 transfers, and approvals across Base, Ethereum, Arbitrum, or Optimism.

Instructions

[On-Chain Intelligence] Decode an EVM transaction: status, fee, method selector, ERC-20 transfers and approvals Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://crypto.caelaralabs.com.

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": {
      "hash": "<hash>"
    },
    "name": "caelara_crypto_tx_hash_decoder"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYesTransaction hash (0x + 64 hex)
chainNoChain: base|ethereum|arbitrum|optimism (default base)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add real context that structured fields cannot: measured p50 12 ms / p95 14 ms latency and the upstream host it calls, and the enumerated fields implicitly define the return content for a read-only operation. It does not cover error behavior (unknown/nonexistent hash, unsupported chain), rate limits, or whether it works for pending transactions.

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 short sentences, front-loaded with the action and its outputs before the performance/host metadata. The bracketed category tag and dated benchmark citation are mild overhead but each sentence still carries 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 two-parameter decode tool with no output schema, the enumeration of decoded fields effectively substitutes for a return-value description, and the latency figures set expectations. Remaining gaps — behavior on invalid hashes and unsupported chains — are minor for a low-risk read operation.

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 100% — the hash format and the chain enum values (base|ethereum|arbitrum|optimism, default base) are fully documented in the schema. The description adds nothing about either parameter, notably never mentioning the chain option, so baseline 3 applies.

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 uses a specific verb ("Decode") on a specific resource ("an EVM transaction") and enumerates the decoded fields: status, fee, method selector, ERC-20 transfers and approvals. That is far more precise than a name restatement. It doesn't position itself against any related tool, but none of the listed siblings is a transaction decoder, so the gap is small.

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?

Usage is only implied: an agent infers it should call this when it holds a transaction hash and needs status/fee/transfer detail. There is no explicit when-not guidance, no mention of what to use instead for address-level or token-level questions (e.g. the ERC-20 inspector sibling), and no stated prerequisites.

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

Deploy Server

Other Tools