Solana Trading & Live Data — PumpView

get_access_status

Read-onlyIdempotent

Inspect the authenticated account's live-data grants, rate limit and feed health.

    Call before consuming data or after an access error. Bearer key required;
    no data credits consumed. Returns unexpired grants (remaining=-1 means
    Unlimited), http_rate_limit shared across account keys, and source health.
    An empty grants list means no unexpired package; a grant can still have zero
    credits. Key-specific budgets are managed in the dashboard and are not in
    this response. Use get_trading_usage for swap volume, get_trading_config for
    swap policy, and get_payment_instructions to create a data-package invoice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`grants`	Yes	Unexpired packages: id, plan, expires (Unix seconds), remaining credits (-1 means unlimited), max_filters and max_connections. Empty means no unexpired grant.
`source`	Yes	Current local feed health: connected/source_connected, last_message_age_seconds, cursor, dropped-event and replay-gap counters.
`http_rate_limit`	Yes	requests_per_second, scope=account, shared_with_mcp=true. The allowance is shared by all keys and HTTP/MCP calls.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing auth requirements ('Bearer key required'), cost behavior ('no data credits consumed'), return semantics ('remaining=-1 means Unlimited', 'empty grants list means no unexpired package', a grant can still have zero credits), and an explicit scope exclusion (key-specific budgets are dashboard-managed and not in this response).

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-loads the purpose, follows with the trigger condition, then the return contract, then sibling routing. Every sentence carries information an agent needs; no filler.

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?

With an output schema present, the description needn't restate return shapes, yet it still adds the interpretive details (unlimited sentinel, empty-list meaning, excluded budgets) that make the response usable. Complete for a no-arg status 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, so the baseline is 4; there are no parameter semantics to add, and the description correctly does not invent any.

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 ('Inspect') and resource ('the authenticated account's live-data grants, rate limit and feed health'), itemizing the three artifacts returned. An agent can distinguish it from sibling status tools like get_swap_status or get_trading_usage 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 ('before consuming data or after an access error') and routes to three named alternatives with their respective domains (get_trading_usage for swap volume, get_trading_config for swap policy, get_payment_instructions for invoices). 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?