Skip to main content
Glama

portal_solana_query_transactions

Retrieve raw Solana transactions with optional balances, rewards, logs, and instruction context. Filter by program, timeframe, or account.

Instructions

Query raw Solana transactions with optional balances, rewards, logs, and instruction context.

COMMON USER ASKS:

  • Recent Solana transactions

  • Filter by program

WHEN TO USE:

  • You need raw Solana transaction records.

  • You want Solana-specific filters or include flags that convenience tools do not expose.

DON'T USE:

  • You only want recent activity or a compact network summary.

EXAMPLES:

  • Recent Solana transactions: {"network":"solana-mainnet","timeframe":"1h","limit":20}

  • Filter by program: {"network":"solana-mainnet","timeframe":"1h","program_id":["TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA"],"limit":20}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax transactions to return (default: 50, max: 200)
cursorNoContinuation cursor from a previous response
networkNoNetwork name or alias. Optional when continuing with cursor.
to_blockNoEnding slot number
fee_payerNoFee payer addresses
timeframeNoTime range (e.g., '1h', '24h'). Alternative to from_block/to_block.
from_blockNoStarting slot number (use this OR timeframe)
include_logsNoInclude program logs
to_timestampNoEnding timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
finalized_onlyNoOnly query finalized slots
from_timestampNoStarting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago".
include_rewardsNoInclude block rewards (validator staking rewards). Filter by pubkey using mentions_account.
response_formatNoResponse format: defaults to 'compact' for chat-friendly output, or stays 'full' when inline instruction, balance, log, or reward context is requested. Use 'summary' for aggregate stats.
include_balancesNoInclude SOL balance changes
mentions_accountNoAccounts mentioned anywhere in the transaction
include_instructionsNoInclude instruction data
include_token_balancesNoInclude SPL token balance changes
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as being read-only, rate limits, or authentication requirements, beyond implying a query operation.

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?

The description is well-structured with sections for purpose, common asks, usage guidelines, and examples. It is front-loaded and each section adds value without being overly verbose.

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?

Despite missing output schema, the description explains response format options and provides examples covering common cases. It addresses pagination and contextual options adequately for a complex tool.

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%, meaning the schema already documents all parameters. The description adds examples but not significant additional meaning, so baseline 3 is appropriate.

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 'Query raw Solana transactions with optional balances, rewards, logs, and instruction context', providing a specific verb and resource. It implies differentiation from convenience tools but doesn't explicitly name sibling tools.

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?

The WHEN TO USE and DON'T USE sections give explicit guidance: use when needing raw Solana records and specific filters, avoid when only recent activity or compact summary is needed. Lacks specific alternative tool names but still useful.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/subsquid-labs/portal-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server