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

@cryptoapis-io/mcp-transactions-data

Official

Solana transaction details

transactions_data_solana
Read-onlyIdempotent

Retrieves Solana transaction details by hash (signature) from mainnet or devnet, enabling verification of on-chain activity and transaction outcomes.

Instructions

Transactions Data Solana: get transaction details by transaction hash (signature). Networks: mainnet, devnet.

Credits per call: 90

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

Input Schema

NameRequiredDescriptionDefault
contextNoOptional context for the request - echoed back in response
networkYesNetwork name
transactionHashYesTransaction hash (signature)

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 readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context in the per-call credit cost (90) and the note that actual credits appear in response headers, but says nothing about failure modes (e.g., unknown hash) or what 'transaction details' includes.

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?

The core purpose is front-loaded in the first sentence and the network scope follows immediately. The credits boilerplate ('indicative only and may change at any time') is slightly padded but still short and relevant to cost-aware callers.

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?

This is a simple single-lookup read tool with full schema coverage and annotations, so most requirements are already met. However, with no output schema, the description never indicates what the returned transaction details comprise, leaving the response shape opaque.

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%, so all three parameters (network enum, transactionHash, context) are already documented in the schema. The description restates the hash-as-signature and network scope without adding format, length, or encoding details beyond what the schema provides — the expected baseline when the schema does the work.

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 states a specific verb and resource ('get transaction details by transaction hash (signature)') and pins the supported networks (mainnet, devnet). The chain is conveyed by name/title rather than a sentence contrasting it with transactions_data_evm or the other chain variants, so sibling differentiation is implied rather than stated.

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?

It implies when the tool applies (you have a Solana signature for mainnet or devnet) and constrains the network values, but gives no explicit when-not guidance or routing to sibling chain tools. An agent must infer the alternatives on its own.

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