Skip to main content
Glama
Sign In
Kaspa MCP

Kaspa MCP

by kasanova-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_transaction

Retrieve transaction status and details using a transaction ID to monitor Kaspa network activity and verify transfers.

Instructions

Get transaction status and details

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": {
      "txId": "<txId>"
    },
    "name": "get_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
txIdYesTransaction ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only states what the tool does, not how it behaves. It lacks details on permissions, rate limits, error handling, or response format, which are critical for a read operation in a financial context.

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

Conciseness5/5

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

The description is extremely concise with a single, front-loaded sentence that directly states the tool's purpose. There is zero wasted text, making it efficient and easy to parse, though this brevity contributes to gaps in other dimensions.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete for a tool that retrieves transaction details. It doesn't explain what 'status and details' include, potential return values, or error scenarios, leaving significant gaps for agent understanding in a financial system context.

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?

The schema description coverage is 100%, with the single parameter 'txId' documented as 'Transaction ID'. The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 clearly states the tool's purpose with a specific verb ('Get') and resource ('transaction status and details'), making it immediately understandable. However, it doesn't differentiate from sibling tools like 'get_balance' or 'send_kaspa' beyond the obvious resource difference, missing explicit sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a transaction ID), exclusions, or comparisons to siblings like 'get_balance' for account info or 'send_kaspa' for transaction creation, leaving usage context implied at best.

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