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

@cryptoapis-io/mcp-transactions-data

Official

Kaspa transaction details

transactions_data_kaspa
Read-onlyIdempotent

Retrieve transaction details by transaction ID on Kaspa mainnet to verify on-chain activity and inspect transaction data.

Instructions

Transactions Data Kaspa: get transaction details by transaction ID. Network: mainnet.

Credits per call: 918

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>",
      "transactionId": "<transactionId>"
    },
    "name": "transactions_data_kaspa"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoOptional context for the request - echoed back in response
networkYesNetwork name
transactionIdYesTransaction ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/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 value beyond them by disclosing cost: 918 credits per call and the caveat that actual credits appear in response headers, which an agent should factor into invocation decisions. It stops short of describing error conditions or response behavior.

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 purpose is front-loaded in the first sentence, which is good, but roughly half the text is billing boilerplate ('Credits per call: 918', 'indicative only and may change at any time'). That information is useful but disproportionately verbose for a three-parameter read tool.

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 simple, fully-documented, read-only lookup with annotations covering the safety profile and no output schema expected, the description supplies what an agent needs: what it does, which network, and what it costs. Missing only explicit sibling routing, which is mild given the chain-specific name.

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%, so the schema already documents network, transactionId and context. The description only restates the mainnet network and transaction-ID lookup, adding no format, length or context-echo semantics beyond the schema. 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?

States a specific verb and resource: 'get transaction details by transaction ID', with the chain pinned by the 'Kaspa' name and 'Network: mainnet'. It is clearly distinguished from chain-specific siblings like transactions_data_evm or transactions_data_solana, though it never names them 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 'by transaction ID' phrasing implies the lookup context, but there is no explicit when-to-use or when-not guidance and no routing to alternatives for other chains or other data types. The agent must infer that this is the Kaspa-specific variant.

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