Solana Trading & Live Data — PumpView

get_stream_connection

Read-onlyIdempotent

Get WSS setup for continuous live trades instead of polling get_recent_trades.

    Requires a Bearer key with an active eligible data grant/budget; 402 means
    access is unavailable. Returns url, an Authorization header template,
    first_message JSON and cursor-resume instructions. This lookup consumes no
    data credits and opens no background connection. Your runtime must connect
    and insert its own key; all keys share one concurrent WSS connection per account.
    Delivered events consume data credits/budget under the plan. Persist the last
    cursor to resume; an expired cursor requires a fresh snapshot and gap handling.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	WSS endpoint to open in the caller runtime.
`resume`	Yes	How to resume with the last received cursor. An expired cursor requires a fresh snapshot.
`first_message`	Yes	Initial JSON subscription message. Customize filters.mints/wallets and filters.after as documented.
`authentication`	Yes	Handshake header template. Supply your own API key; the response never echoes the secret.

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?

Annotations declare read-only/idempotent/no-destruction, and the description still adds substantial operational context beyond them: this lookup consumes no data credits and opens no connection, the runtime must connect and supply its own key, only one concurrent WSS connection exists per account, delivered events do bill credits, and cursors must be persisted with defined expiry behavior. This is exactly the kind of disclosure annotations cannot carry.

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?

Front-loaded with purpose and the polling alternative, then packed with operational constraints. Every sentence carries new information, though the single dense paragraph could be broken into bullets for scanability.

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 values need not be explained, yet the description still notes the shape (url, Authorization header template, first_message, cursor-resume steps). Auth requirements, credit implications, concurrency limits, and cursor lifecycle are fully covered for a streaming-setup 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?

The tool takes zero parameters with 100% schema coverage, so there is nothing parametric to document; baseline for a no-parameter tool applies. The description correctly does not invent parameter guidance.

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 ('Get WSS setup for continuous live trades') and immediately contrasts it with the polling alternative get_recent_trades. An agent can distinguish this from every other sibling without opening a 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?

Explicitly says to use this 'instead of polling get_recent_trades', names the prerequisite (Bearer key with an active eligible data grant/budget), and gives the failure signal (402 = access unavailable). When-to-use, alternative, and precondition are all present.

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?