Solana Trading & Live Data — PumpView

get_recent_trades

Read filtered market swap summaries from PumpView's supported SOL-pair feed.

    Use for recent market activity, not your submitted swap receipt (get_swap_status).
    Requires a Bearer key, active data grant and sufficient key budget. Each call
    consumes max(1, returned event count) credits; repeated reads also count.
    Unlimited has no package event cap, but an explicit key budget still applies.
    Returns events in feed order, a cursor and health. Filtering follows batch
    scanning, so advance using the returned cursor even for an empty batch.
    On 409 cursor_expired restart without after and record a gap; 402 means access
    or budget exhausted, 503 means unavailable source. Use get_stream_connection
    for continuous WSS delivery. Amounts are decoder floats, not full transaction accounting.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_recent_trades"
  }
}

Input Schema

Name	Required	Description
`mint`	No	Optional exact token mint address in base58. Filters the traded token of the supported SOL-pair feed; omit for all mints. No ticker aliases.
`after`	No	Opaque cursor returned by the previous batch. Omit for a recent snapshot; supply unchanged to scan subsequent events. Not a timestamp or transaction signature.
`limit`	No	Maximum accepted events scanned before mint/wallet filters, 1-500; default 100. The number returned can be smaller, including zero.
`wallet`	No	Optional exact base58 trader public key reported by the decoder. Combined with mint using AND; omit for all wallets.

Output Schema

Name	Required	Description
`cursor`	Yes	Resume position after the scanned batch, including events removed by filters; use as the next after value.
`events`	Yes	Accepted events after mint/wallet filtering. May be empty even when the cursor advances.
`health`	No	Feed connection status, last-message age, drop/replay-gap counters and price_filter identifier.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes far beyond the annotations: auth requirements (Bearer key, active data grant, sufficient budget), a precise cost formula (max(1, returned event count) credits, repeated reads billed), package-cap behavior, feed ordering, and per-status-code recovery instructions for 409/402/503 including the 'restart without after and record a gap' action. The credit-charging detail also substantiates the non-idempotent annotation.

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?

Purpose is front-loaded in the first clause, then alternatives, then operational constraints. The dense error-code and credit sentences are load-bearing rather than filler, though the block reads as a wall of prose that could be tightened with list structure.

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?

An output schema exists so return shape needn't be spelled out, yet the description still names the returned cursor and health, which are the fields an agent must act on. Auth, budget, pagination, error recovery, and stream alternative are all covered for a 4-param open-world read tool.

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

Parameters4/5

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

Schema coverage is 100% so the baseline is 3, but the description adds genuinely non-schema semantics: filtering happens after batch scanning, so an empty batch still requires advancing with the returned cursor, and a 409 requires retrying without 'after'. That clarifies how after/limit/mint/wallet interact rather than restating them.

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?

States a specific verb and resource ('Read filtered market swap summaries from PumpView's supported SOL-pair feed') with clear scope, and immediately distinguishes itself from the closest sibling by naming get_swap_status as the receipt tool. An agent can tell this apart from get_stream_connection and get_swap_status without opening any schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ('recent market activity'), explicit when-not ('not your submitted swap receipt'), and names two alternatives with their selecting conditions: get_swap_status for receipts and get_stream_connection for continuous WSS delivery. Nothing is left to inference.

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

All Solana Trading & Live Data — PumpView tools Inspect

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

Need Help?