Skip to main content
Glama
Sign In

Solscan

by io.github.pipeworx-io
OverviewDiscussionsAdmin

List Transfers

list_transfers
Read-onlyIdempotent

Recent SOL and SPL token transfers for an account. Returns signature, timestamp, side (sent/received), token, amount, counterparty. Pro tier — requires your own Solscan API key (Pipeworx's platform key is Free tier and cannot call this).

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page (default 1)
addressYesSolana account public key
page_sizeNo1-40 (default 20)

Output Schema

NameRequiredDescriptionDefault
dataYesPaginated transfer history with signature, timestamp, side, token, amount, counterparty
pathYesAPI endpoint path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "address": "SolendFtLatfDwGrPfLVLocked111111111111111"
+  },
+  {
+    "address": "SolendFtLatfDwGrPfLVLocked111111111111111",
+    "page": 1,
+    "page_size": 30
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Paginated transfer history with signature, timestamp, side, token, amount, counterparty",
+      "type": "object"
+    },
+    "path": {
+      "description": "API endpoint path",
+      "type": "string"
+    }
+  },
+  "required": [
+    "path",
+    "data"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds a genuinely non-obvious constraint — this endpoint requires the caller's own Solscan API key because the platform key is Free tier — which prevents a predictable failure. It does not say what 'recent' covers or how pagination terminates.

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 short sentences, front-loaded with purpose, then return shape, then the blocking prerequisite. Nothing is redundant with the title or schema.

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?

Output schema exists, so return values needn't be spelled out, and the tier/key prerequisite is a strong addition for a shallow 3-parameter tool. The remaining gap is the undefined recency window and result-set bounds, which matter for an agent deciding whether this surface is sufficient.

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 page/page_size/address are all documented there, so the baseline is 3. The description adds only the implicit notion of recency and no clarification of page_size limits or total-result behavior beyond the schema.

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+resource ('Recent SOL and SPL token transfers for an account') and enumerates the returned fields, so the agent knows exactly what it gets. It does not name sibling tools like get_transaction or get_dex_activity, so differentiation is implied 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 Guidelines3/5

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

Usage is implied by 'for an account' — use when you need transfer history rather than a single transaction or DEX swap activity — but no when-not conditions or named alternatives are given. The Pro tier warning is helpful call-environment context rather than usage 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