Skip to main content
Glama

Check a Solana transaction's status, fee and balance changes

solana_tx
Read-only

A Solana transaction by signature: status, time, fee in SOL and USD, signers, SOL balance changes per account, token balance changes (mint, owner, change) and the programs it invoked. Read-only; nothing is sent. A very new signature may be missing (404, not charged). Related tools on this server, for a different need: solana_account when you need a Solana account: lamports and SOL with a USD value, owner; solana_quote when you need Best Jupiter swap route for a Solana token pair. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "solana_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
signatureYesTransaction signature, base58

Output Schema

NameRequiredDescriptionDefault
feeNo
slotNo
timeNo
errorNo
sourceNo
statusNo
signersNo
programsNo
checkedAtNo
signatureNo
disclaimerNo
solChangesNo
tokenChangesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description still earns credit for the failure mode 'A very new signature may be missing (404, not charged)' and the billing terms ('$0.002 per successful call... failed calls are not charged'), which are genuine operational context not present in structured fields. It stops short of saying what a not-yet-confirmed or failed transaction returns.

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?

Front-loaded with the resource and payload, then read-only status, then the 404 caveat, then sibling routing and pricing. It is efficient overall, though the returned-field list is a long run-on and the sibling/pricing tail reads as boilerplate that could be trimmed.

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?

Low-complexity read-only tool with one required param, a full schema, and an output schema, so return-value explanation is not required — the description provides extras (cost, 404 behavior, alternatives) instead. Nothing essential for a correct call is missing, though confirmation-state semantics could round it out.

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?

There is a single parameter with 100% schema description coverage ('Transaction signature, base58'), so the schema carries the burden. The description restates only that lookup is 'by signature' without adding format, validation, or edge-case guidance beyond what the schema says — baseline 3.

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?

The description names a specific resource and key ('A Solana transaction by signature') and enumerates exactly what comes back: status, time, fee in SOL and USD, signers, SOL balance changes per account, token balance changes (mint, owner, change) and invoked programs. That makes it trivially distinguishable from solana_account (lamports/owner) and solana_quote (swap routes), which are named explicitly.

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

Usage Guidelines4/5

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

It routes the agent to alternatives with conditions: 'solana_account when you need a Solana account...', 'solana_quote when you need Best Jupiter swap route...'. What's missing is an explicit when-not or a statement that this tool is the wrong choice for pending/unconfirmed signatures beyond the brief 404 note.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources