Skip to main content
Glama
Sign In

SiteCheck

by io.github.bck-stack
OverviewDiscussionsAdmin

Solana wallet holdings: SOL and every SPL / Token-2022

solana_wallet
Read-only

Solana wallet holdings: SOL and every SPL / Token-2022 balance with name, symbol, USD price and value (Jupiter), sorted by value, plus the total in USD. Dust and unpriced tokens hidden unless includeDust=1. Information only. Related tools on this server, for a different need: solana_account when you need a Solana account: lamports and SOL with a USD value, owner; solana_quote when you need Best Jupiter swap route for a Solana token pair. Price: $0.003 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "address": "<address>"
    },
    "name": "solana_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesSolana wallet address (base58)
includeDustNo1 = also list tokens worth under $0.01 or without a price

Output Schema

NameRequiredDescriptionDefault
solNo
tokensNo
addressNo
disclaimerNo
tokensShownNo
tokenAccountsNo
totalValueUsdNo
hiddenDustOrUnpricedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "address": {},
+    "disclaimer": {},
+    "hiddenDustOrUnpriced": {},
+    "sol": {},
+    "tokenAccounts": {},
+    "tokens": {},
+    "tokensShown": {},
+    "totalValueUsd": {}
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses filtering behavior (dust and unpriced tokens hidden unless includeDust=1), result ordering, the Jupiter price source, and a metered cost model ($0.003 USDC per successful call via x402, failed calls free). That billing detail is exactly the kind of behavior an agent cannot infer from the schema.

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-loaded with the payload and its fields, then filtering, then alternatives, then price — a sensible priority order. The sibling sentences are grammatically tangled ('solana_account when you need a Solana account: lamports and SOL with a USD value, owner'), costing some readability but not content.

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?

For a two-parameter read tool with an output schema and annotations already in place, the description covers payload composition, filtering defaults, ordering, pricing, and sibling routing. Nothing an agent needs to invoke it correctly 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 description coverage is 100%, so both parameters are already documented. The description's note about dust and unpriced tokens restates the includeDust schema text rather than adding a new threshold, format, or edge case; address receives no extra semantics. 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?

The description opens with a specific verb and resource ('Solana wallet holdings: SOL and every SPL / Token-2022 balance'), enumerates returned fields (name, symbol, USD price, value, total), and states sort order. It clearly separates this from solana_account, solana_quote, and the other solana_* siblings.

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

Usage Guidelines4/5

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

It explicitly routes the agent to two alternatives with the condition that selects each ('solana_account when you need... lamports and SOL... owner', 'solana_quote when you need Best Jupiter swap route'). No explicit 'do not use' framing and the token-metadata sibling solana_token is unaddressed, so it stops short of a perfect routing guide.

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

All SiteCheck toolsInspect
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