Solana Wallet Intel

wallet_quick_batch

Read-onlyIdempotent

Quick screen (windowed realized PnL, win rate, copyTradeScore, copyTradeGrade, bot, exchange, net-winner and dormant flags) for up to 10 Solana wallets in one paid call, ranked by realized PnL. Pass addresses comma-separated. Costs $0.015 USDC (15000 base units) via x402. The same price is charged for HTTP GET /wallet/quick/batch. An unpaid HTTP call returns 402 even when the query is missing or invalid. A signed call with invalid arguments is rejected before settlement and is not charged. A successful result can set cached, stale, and cacheAgeMs. stale true means a previous result was served while a refresh runs or the upstream failed. You are charged only when the tool result is not an error.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "addresses": "<addresses>"
    },
    "name": "wallet_quick_batch"
  }
}

Input Schema

Name	Required	Description	Default
`addresses`	Yes	1 to 10 comma-separated base58 Solana wallet addresses.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026
RemovedOct 23, 2026
First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses cost ($0.015 USDC via x402), the equivalent HTTP endpoint, that unpaid calls return 402 even on invalid queries, that signed calls with invalid args are rejected pre-settlement, and that charges apply only on non-error results. It also explains cached/stale/cacheAgeMs semantics, which 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.

Conciseness4/5

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

Purpose and cost are front-loaded, followed by settlement and caching caveats in logical order. Slight redundancy between the $0.015 pricing line and the 'same price for HTTP GET' line, but overall tight for the amount of behavioral detail conveyed.

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?

No output schema exists, but the description enumerates the returned fields (realized PnL, win rate, copyTradeScore/grade, bot, exchange, net-winner/dormant flags) plus cache metadata, and covers billing edge cases. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter already documents '1 to 10 comma-separated base58 addresses'. The description's 'Pass addresses comma-separated' largely restates that, adding no new syntax, format, or validation detail, so baseline 3 applies.

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 ('Quick screen ... for up to 10 Solana wallets in one paid call'), names the metrics returned, and the batch/one-call framing implicitly separates it from the single-wallet sibling wallet_quick. An agent can identify this as the bulk variant without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the 'up to 10' cap and comma-separated input, and the pricing/settlement notes clarify the paid context. However, it never explicitly routes the agent to wallet_quick for single wallets or states when not to use batch, leaving the sibling choice 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 Wallet Intel 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?