PumpView — Solana Trading & Live Data

get_trading_config

Read-onlyIdempotent

Read the current server's swap policy before choosing build_swap parameters.

    Public: no API key or data credits needed. Returns enabled, mint aliases,
    allowed pair assets, fee basis points, USD minimums, tip limits and build TTL.
    enabled is configuration status, not a liquidity quote or an RPC health check.
    Use get_trading_usage for executed account volume and get_access_status for grants.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`tips`	Yes	Minimum tip in lamports and transfer recipients disclosed for review before signing.
`enabled`	Yes	Whether the trading proxy is currently configured and enabled; not a guarantee that a route exists.
`mint_aliases`	Yes	SOL, WSOL and USDC alias-to-mint mapping. SOL spends native balance; WSOL spends SPL balance.
`slippage_bps`	Yes	Whether explicit slippage is required and its inclusive minimum/maximum in basis points.
`free_minimum_usd`	Yes	Minimum swap value in USD without an active Unlimited grant, as a decimal string.
`platform_fee_bps`	Yes	Platform swap fee in basis points; 50 means 0.5%.
`build_ttl_seconds`	Yes	Time window for submitting a newly built transaction before its unsigned intent expires.
`receipt_commitment`	Yes	Earliest commitment at which execution receipts are available: confirmed.
`required_pair_assets`	Yes	At least one swap leg must resolve to an asset in this list; see mint_aliases.
`subscription_required`	Yes	False: building and submitting swaps needs no paid data package.
`unlimited_minimum_usd`	Yes	Minimum swap value in USD with Unlimited, as a decimal string.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds meaningful context beyond them: no API key or data credits required (public access), the precise nature of 'enabled' as configuration status rather than a liquidity quote or RPC health check, and the shape of the payload. That negative clarification is exactly the kind of disambiguation annotations cannot express. Slightly short of 5 only because it doesn't mention caching/TTL semantics of the config itself, despite build TTL being a returned field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and the reason to call it, then access requirements, then payload contents, then boundary clarifications. Every sentence earns its place and none repeat the schema or annotations.

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 enumerated, yet the description still names the key fields and, more importantly, defines 'enabled' and separates configuration status from liquidity and RPC health. Combined with the sibling routing, an agent has everything needed to call this correctly.

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 and there is nothing for the description to clarify about inputs. The description instead spends its budget on returned fields, which is appropriate rather than a gap.

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+resource ('Read the current server's swap policy') with the exact downstream purpose ('before choosing build_swap parameters'). It is immediately distinguishable from sibling reads like get_trading_usage and get_access_status. No ambiguity about what is returned versus what this tool is not.

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 routes: use this before calling build_swap, use get_trading_usage for executed volume, use get_access_status for grants. Both the condition for using this tool and the alternatives for adjacent needs are named, leaving nothing to inference.

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.