Solana Trading & Live Data — PumpView

get_trading_usage

Read-onlyIdempotent

Read all-time executed volume for the authenticated account and each API key.

    Use for accounting, not market history (get_recent_trades) or one receipt
    (get_swap_status). Bearer key required; no data package or credits consumed.
    Returns available, totals and by_api_key. Successful swaps count once from
    confirmed; finalization never adds them again. SOL/USDC amounts are decimal
    strings; USD uses build-time prices. available=false means temporary
    unavailability, not zero volume. Newly confirmed receipts may appear shortly later.

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_trading_usage"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`period`	No	Aggregation period: all_time.
`totals`	No	All-time executed account volume and count when available.
`message`	No	Explanation when statistics are unavailable.
`available`	Yes	False means statistics are temporarily unavailable, not that volume is zero.
`by_api_key`	No	Per-key volume buckets. An unused key may have no bucket yet.
`counted_from`	No	Earliest counted commitment: confirmed; finalization does not add volume again.

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: bearer key requirement, no credit consumption, the once-per-swap counting rule, decimal-string vs build-time-price formatting, the meaning of available=false, and eventual-consistency lag for new receipts. These are exactly the operational details annotations cannot convey.

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?

Purpose is front-loaded in the first sentence, followed by routing guidance, then behavioral caveats. Every sentence carries distinct information; nothing is repeated from 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-value detail is not strictly needed, yet the description still summarizes the return shape (available, totals, by_api_key) and covers auth, cost, counting semantics, and edge cases. Complete for an agent to call and interpret 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The description correctly does not waste space restating a nonexistent 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+resource+scope: 'Read all-time executed volume for the authenticated account and each API key.' It explicitly distinguishes itself from get_recent_trades (market history) and get_swap_status (one receipt), so an agent can route 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?

Gives an explicit use case ('use for accounting') and names both excluded alternatives with the reason each is wrong for this need. No inference required to pick between the three siblings.

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?