Skip to main content
Glama
Sign In

Solscan

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Transaction

get_transaction
Read-onlyIdempotent

Fetch a Solana transaction by base58 signature. Returns status (Success/Fail), slot, block time, fee in lamports, SOL balance changes per account, and parsed instruction list. Pro tier — requires your own Solscan API key (Pipeworx's platform key is Free tier and cannot call this).

Input Schema

NameRequiredDescriptionDefault
signatureYesSolana transaction signature (base58)

Output Schema

NameRequiredDescriptionDefault
dataYesTransaction detail: status, slot, block time, fee, balance changes, parsed instructions
pathYesAPI endpoint path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "signature": "5h6xBEauJ3jGaDررrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Transaction detail: status, slot, block time, fee, balance changes, parsed instructions",
+      "type": "object"
+    },
+    "path": {
+      "description": "API endpoint path",
+      "type": "string"
+    }
+  },
+  "required": [
+    "path",
+    "data"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description still adds real value by disclosing the paid-tier/API-key requirement that would otherwise cause a silent failure on the platform key.

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?

Three sentences, each load-bearing: what it fetches, what it returns, and the access constraint. The identifying resource and key are front-loaded.

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

Completeness5/5

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

With an output schema present, the return-value sentence is a convenience rather than a necessity, and the auth/tier caveat is the one thing an agent cannot learn from structured fields. Nothing needed to call this correctly is missing.

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% and there is exactly one parameter, whose description ('Solana transaction signature (base58)') matches what the tool description repeats. No extra semantics such as format validation or failure behavior for a bad signature are provided.

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 plus the lookup key: 'Fetch a Solana transaction by base58 signature.' That is enough to separate it from the list-style sibling get_network_transactions, but no sibling is named, so the differentiation is inferred rather than explicit.

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?

Gives a clear usage precondition that no other field carries: 'Pro tier — requires your own Solscan API key (Pipeworx's platform key is Free tier and cannot call this).' It does not name alternatives for the list/count use case, so it stops short of full when/when-not guidance.

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

All Solscan toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources