solana-mcp-server

Get transaction

get_transaction

Read-only

Fetches a Solana transaction by signature and returns a compact summary of status, fee, signers, called programs, and SOL/token balance changes.

Instructions

Fetches a transaction by signature and returns a compact summary: status, fee, signers, programs called, SOL and token balance changes.

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

Input Schema

Name	Required	Description	Default
`signature`	Yes	Base58 transaction signature
`includeLogs`	No	Include program logs (truncated to 50 lines)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful context beyond that: the return is a 'compact summary' rather than full raw transaction data, which calibrates agent expectations about fidelity. It does not mention error behavior for unknown signatures or rate limits, keeping it short of a 5.

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?

A single front-loaded sentence with the resource first and the return payload enumerated compactly. No filler, no repetition of the title.

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?

With no output schema, the description carries the burden of describing return values, and it does so by listing the summary fields. Both parameters are fully documented in the schema and the read-only nature is annotated. Only minor gaps remain, such as not-found behavior and whether logs are off by default.

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%: both the signature format (Base58) and includeLogs truncation to 50 lines are documented in the schema itself. The description adds nothing about parameters, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (fetches) and resource (a transaction by signature) and enumerates the returned content: status, fee, signers, programs called, SOL and token balance changes. This clearly separates it from siblings like get_balance, get_token_accounts, recent_activity, and simulate_transfer, which operate on accounts, lists, or simulations rather than a single known transaction.

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 required signature: this is the lookup to use when you already have a transaction signature. However, the description never states when to prefer it over recent_activity for browsing transactions, nor any preconditions or exclusions.

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

Deploy Server