Skip to main content
Glama
@cryptoapis-io/mcp-transactions-data

@cryptoapis-io/mcp-transactions-data

Official

EVM transaction details

transactions_data_evm
Read-onlyIdempotent

Fetch transaction details, internal transactions, token transfers, or logs by transaction hash across supported EVM blockchains and networks.

Instructions

Transactions Data EVM: get transaction details, internal transactions, token transfers, or logs by transaction hash.

Actions: get-transaction-details, list-internal-transactions, list-token-transfers, list-logs.

Credits by action (source: OpenAPI): • get-transaction-details: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 • list-internal-transactions: arbitrum 512, avalanche 576, base 384, binance-smart-chain 800, ethereum 320, ethereum-classic 416, optimism 448, polygon 640, tron 480 • list-logs: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 • list-token-transfers: arbitrum 352, avalanche 396, base 264, binance-smart-chain 550, ethereum 220, ethereum-classic 286, optimism 308, polygon 440, tron 330

Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.

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": {
      "action": "<action>",
      "blockchain": "<blockchain>",
      "network": "<network>",
      "transactionHash": "<transactionHash>"
    },
    "name": "transactions_data_evm"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction to perform
contextNoOptional context for the request - echoed back in response
networkYesNetwork name
blockchainYesBlockchain protocol
transactionHashYesTransaction hash

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine behavior beyond that: per-action, per-chain credit costs and the caveat that actual spend is only reported in response headers, which lets an agent reason about cost before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening line and action list are front-loaded and easy to scan, but the credit section consumes the majority of the text with repetitive per-chain enumeration that could be compressed. The closing disclaimer further pads an already long definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does not describe what any of the four actions return (transaction fields, transfer shape, log entries), nor whether results are paginated or limited. For a read-only tool with four required parameters and four distinct result shapes, that leaves a meaningful gap.

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% and three parameters carry enums, so the schema already carries most of the load. The credit table does add a cost dimension tied to the action×blockchain combination that the schema cannot express, but it does not clarify the network-vs-blockchain distinction (mainnet/testnet vs protocol), which is the one genuinely ambiguous pairing.

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 names the resource (EVM transaction details) and enumerates the four concrete operations (get-transaction-details, list-internal-transactions, list-token-transfers, list-logs) keyed by transaction hash. The blockchain list in the credit section makes clear this covers EVM-style chains, which distinguishes it structurally from the sibling chain-specific tools, though no sibling is named explicitly.

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?

The action list implies which operation to pick for each need, and the credit table surfaces a real selection trade-off (list-internal-transactions costs roughly 2.7x get-transaction-details on the same chain). There is no explicit when-to-use/when-not guidance and no statement about alternatives such as a block- or address-oriented tool.

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