Skip to main content
Glama

Find Solana transactions

portal_solana_query_transactions
Read-only

Retrieve raw Solana transactions with optional balances, rewards, logs, and instruction context. Filter by program, account, or time range to inspect specific on-chain activity.

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_uiNoOptional chart, table, and follow-up presentation metadata.
_llmNoHints that help an AI client locate the primary evidence.
_metaNoNetwork, block range, timing, and row-count metadata.
errorNoStructured failure details when the tool cannot complete the request.
itemsNoPrimary result rows when the tool returns a list.
valueNoPrimary result when the tool returns a scalar value.
answerNoConcise answer grounded in the returned blockchain data.
_noticeNoImportant limitation or truncation notice.
displayNoPlain-language labels for presenting the result.
_noticesNoImportant limitations or truncation notices.
_summaryNoHuman-readable summary of the result.
_coverageNoCompleteness of the requested window and result set.
_evidenceNoReplayable arguments, exact-data digest, row count, and completeness receipt.
_orderingNoOrdering guarantees for the returned data.
_executionNoBounded execution and scan details.
_freshnessNoFreshness and finality information for the returned data.
next_stepsNoSafe follow-up actions and continuation guidance.
_paginationNoPagination state and an optional continuation cursor.
investigationNoEvidence paths, useful pivots, and result limitations.
pipes_handoffNoOptional SQD Pipes guidance for custom data needs.
_tool_contractNoTool identity, intent, and supported blockchain families.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.8.3
    • addedOutput schema / properties / _evidence
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Replayable arguments, exact-data digest, row count, and completeness receipt.",
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
  2. Changed7 schema fields changedv0.8.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / from_timestamp / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / from_timestamp / type
      Removed value: -[
      -  "number",
      -  "string"
      -]
    • addedInput schema / properties / to_timestamp / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / to_timestamp / type
      Removed value: -[
      -  "number",
      -  "string"
      -]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "_coverage": {
      +      "description": "Completeness of the requested window and result set."
      +    },
      +    "_execution": {
      +      "additionalProperties": {},
      +      "description": "Bounded execution and scan details.",
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "_freshness": {
      +      "description": "Freshness and finality information for the returned data."
      +    },
      +    "_llm": {
      +      "description": "Hints that help an AI client locate the primary evidence."
      +    },
      +    "_meta": {
      +      "additionalProperties": {},
      +      "description": "Network, block range, timing, and row-count metadata.",
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "_notice": {
      +      "description": "Important limitation or truncation notice.",
      +      "type": "string"
      +    },
      +    "_notices": {
      +      "description": "Important limitations or truncation notices.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "_ordering": {
      +      "description": "Ordering guarantees for the returned data."
      +    },
      +    "_pagination": {
      +      "additionalProperties": {},
      +      "description": "Pagination state and an optional continuation cursor.",
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "_summary": {
      +      "description": "Human-readable summary of the result.",
      +      "type": "string"
      +    },
      +    "_tool_contract": {
      +      "additionalProperties": {},
      +      "description": "Tool identity, intent, and supported blockchain families.",
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "_ui": {
      +      "description": "Optional chart, table, and follow-up presentation metadata."
      +    },
      +    "answer": {
      +      "description": "Concise answer grounded in the returned blockchain data.",
      +      "type": "string"
      +    },
      +    "display": {
      +      "additionalProperties": {},
      +      "description": "Plain-language labels for presenting the result.",
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "error": {
      +      "additionalProperties": {},
      +      "description": "Structured failure details when the tool cannot complete the request.",
      +      "properties": {
      +        "code": {
      +          "type": "string"
      +        },
      +        "origin": {
      +          "type": "string"
      +        },
      +        "retry_after_ms": {
      +          "type": "number"
      +        },
      +        "retryable": {
      +          "type": "boolean"
      +        },
      +        "suggestions": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "summary": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "code",
      +        "origin",
      +        "summary",
      +        "retryable",
      +        "suggestions"
      +      ],
      +      "type": "object"
      +    },
      +    "investigation": {
      +      "additionalProperties": {},
      +      "description": "Evidence paths, useful pivots, and result limitations.",
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "items": {
      +      "description": "Primary result rows when the tool returns a list.",
      +      "items": {},
      +      "type": "array"
      +    },
      +    "next_steps": {
      +      "additionalProperties": {},
      +      "description": "Safe follow-up actions and continuation guidance.",
      +      "properties": {
      +        "actions": {
      +          "items": {
      +            "additionalProperties": {},
      +            "propertyNames": {
      +              "type": "string"
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "continuation": {
      +          "additionalProperties": {},
      +          "propertyNames": {
      +            "type": "string"
      +          },
      +          "type": "object"
      +        },
      +        "custom_data": {
      +          "additionalProperties": {},
      +          "propertyNames": {
      +            "type": "string"
      +          },
      +          "type": "object"
      +        }
      +      },
      +      "required": [
      +        "actions"
      +      ],
      +      "type": "object"
      +    },
      +    "pipes_handoff": {
      +      "description": "Optional SQD Pipes guidance for custom data needs."
      +    },
      +    "value": {
      +      "description": "Primary result when the tool returns a scalar value."
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observedv0.7.9

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds the 'raw' scope and optional context fields, but does not describe behavior such as pagination, response_format defaults, or limitations. It is adequate but does not go beyond what the schema and annotations already imply.

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 scannable sections, front-loaded purpose, and useful examples. The typo in 'DON'T' and slight redundancy in COMMON USER ASKS are minor; overall every section earns its place.

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

Completeness3/5

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

For a 17-parameter tool with no required parameters, the examples and high-level categories provide useful orientation, and the output schema covers return values. However, the documented 'Filter by program' flow is not actually supported by the schema, and there is no guidance on block-vs-timefilter selection, leaving real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, and the description does group include_* flags into meaningful context. However, the examples prominently use program_id for 'Filter by program' while program_id is not present in the input schema. An agent following the example could make an invalid call, which is a significant semantic flaw.

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 states a specific verb and resource: 'Query raw Solana transactions' with optional balances, rewards, logs, and instruction context. It clearly distinguishes this from convenience or recent-activity tools and from non-Solana network siblings.

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?

Explicit WHEN TO USE and DON'T USE sections give clear selection criteria: choose this for raw Solana transaction records or Solana-specific filters, not for recent activity or a compact network summary. It does not name the exact sibling tool such as portal_get_recent_activity, so it stops slightly short of strongest routing.

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

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