PumpView — Solana Trading & Live Data

list_data_plans

Read-onlyIdempotent

List current data packages and prices before buying a live-data subscription.

    Public: no key or credits needed. Returns plan IDs, price in atomic USDC
    (6 decimals), duration, event allowance, filters, account request/connection
    limits and sales_enabled. -1 credits means Unlimited. Trading alone needs
    no data package. If sales are enabled, choose a plan and call
    get_payment_instructions with its exact id to create an unpaid invoice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`unit`	Yes	How delivered events and empty queries consume credits.
`plans`	Yes	Currently configured prepaid data packages and exact prices.
`network`	Yes	Payment network, Solana mainnet.
`base_url`	Yes	Public API origin for optional HTTP access.
`currency`	Yes	Payment currency: native Solana USDC, 6 decimals.
`sales_enabled`	Yes	Whether new data-package invoices can currently be created.
`payment_protocol`	Yes	PumpView invoice protocol, no Coinbase dependency.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 16, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive with openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: it is public with no key or credits required, and it explains the '-1 credits means Unlimited' sentinel and the sales_enabled gating that determines whether a purchase path exists at all.

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-loads the purpose, then access model, then return fields, then the next action - a logical progression with no filler sentences. It runs longer than strictly necessary given the output schema already enumerates the returned fields, but each sentence still carries operational meaning.

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?

The tool has no parameters and a rich output schema, so the description only needs to supply access requirements, sentinel semantics, and workflow routing - and it delivers all three. Nothing an agent needs to call this correctly is missing.

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?

Zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The field-level detail it provides (USDC 6-decimal pricing, duration, event allowance, request/connection limits) describes outputs rather than inputs and is partly redundant with the output schema.

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 ('List current data packages and prices') and immediately scopes the purpose ('before buying a live-data subscription'). An agent can distinguish it from sibling inventory tools like get_trading_config or get_payment_instructions 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 when to call it (before buying a subscription), when it is unnecessary ('Trading alone needs no data package'), and what to do next ('choose a plan and call get_payment_instructions with its exact id'). The alternative tool is named by name.

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

All PumpView — Solana Trading & Live Data 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.