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

@cryptoapis-io/mcp-transactions-data

Official

UTXO transaction details

transactions_data_utxo
Read-onlyIdempotent

Retrieve UTXO blockchain transaction details or raw transaction data by hash across Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, and Zcash on mainnet or testnet.

Instructions

Transactions Data UTXO: get transaction details or raw transaction data by hash.

Actions: get-transaction-details, get-raw-transaction-data. Blockchains: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash. Networks: mainnet, testnet.

Credits by action (source: OpenAPI): • get-raw-transaction-data: bitcoin 110, bitcoin-cash 132, dash 121, dogecoin 121, litecoin 121, zcash 143 • get-transaction-details: bitcoin 110, bitcoin-cash 132, dash 121, dogecoin 121, litecoin 121, zcash 143

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_utxo"
  }
}

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

B3.4/5.0
Behavior3/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 usefully adds per-action credit pricing and clarifies that quoted costs are indicative and that actual spend appears in response headers, which is genuine behavioral value beyond the annotations. It still omits what distinguishes the two actions in output terms and any handling of unconfirmed or unknown hashes.

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 sentence and the Actions/Blockchains/Networks header lines are tightly front-loaded and earn their place. The credit table, however, is bloated: the two action lines carry identical values for all six chains, so the same information could be stated once, and the surrounding caveat prose is lengthy relative to the payload.

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 read-only lookup with full schema coverage, four required parameters and no output schema, the definition supplies everything needed to construct a valid call: actions, chains, networks, hash requirement and cost expectations. What remains thin is solely the semantic distinction between the two actions, which is not enough of a gap to drop below 4.

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 of five parameters are enums, so the schema already documents action, blockchain, network and transactionHash. The description restates the action and blockchain values rather than adding meaning, and says nothing about format expectations for transactionHash or the purpose of the optional context echo, 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 definition opens with a specific verb and resource: 'get transaction details or raw transaction data by hash,' and enumerates the two actions plus the supported blockchains (bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash) and networks. That list implicitly differentiates it from the UTXO-vs-EVM/Solana/XRP siblings, though it never names an alternative 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?

Usage is implied by the blockchain and network enumerations: an agent can infer this is the tool for UTXO-chain transaction lookups and that siblings cover other chains. However, there is no explicit when-to-use/when-not guidance, no statement about choosing between the two actions, and no prerequisites such as whether the hash must be a confirmed transaction.

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