Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

tool_sol_tokens

[x402 paid: $0.002 USDC on Base] SPL token holdings for any Solana address, top balances via live RPC. Body: {address}. tools/call returns the live payment challenge.

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": "tool_sol_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden, and it does disclose non-obvious traits: the $0.002 USDC x402 charge, that data comes from live RPC, and that tools/call returns a live payment challenge rather than data. It omits what happens after payment (format, how many "top" balances, ordering, failure modes when the address is invalid or unfunded), which matters for a paid call.

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?

Three compact segments with the price barrier front-loaded, then the purpose, then the input shape and payment behavior. The fragments ("Body: {address}", "tools/call returns the live payment challenge") are terse to the point of being cryptic, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter paid tool with no output schema, an agent needs the payment handshake and the input contract, and both are present at a skeletal level. What is missing is any picture of the returned payload, so an agent cannot plan post-payment handling or know how "top" is bounded.

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 schema declares zero properties, so the baseline is 4, but the note "Body: {address}" is genuinely additive because it is the only place the required input is stated anywhere in the definition. The mismatch between an empty schema and a required body address is a real ambiguity, though the description errs toward being more informative rather than less.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"SPL token holdings for any Solana address" states a specific resource and scope, and "top balances via live RPC" adds the data source, which is enough to distinguish it from the native-balance sibling sol-balance. It falls short of a 5 because the retrieval verb is nominalized ("holdings") and no sibling is explicitly named as the wrong choice.

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 only implied: the agent must infer that this is the tool to pick for a Solana address's token list rather than native SOL. The price tag front-loading is useful context for deciding to call it, but there is no when-not-to-use statement and no comparison against sol-balance or the token-audit tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources