Skip to main content
Glama

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

sol-balance

[x402 paid: $0.005 USDC on Base] SOL balance for any Solana address, live RPC (?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": "sol-balance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does so for the most consequential trait: it declares a paid x402 call ($0.005 USDC on Base) and explains that tools/call returns the live payment challenge rather than data. It does not cover rate limits, failure/payment-failure behavior, or the shape of the returned balance, so it stops short of full disclosure.

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?

Very short and front-loaded with the cost and payment mechanism, then the purpose, then the parameter form. Every clause carries information; the only cost is that the terse phrasing leaves the schema/parameter mismatch unaddressed.

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-param, no-output-schema, no-annotation tool the description covers purpose, pricing, and the payment challenge flow, but omits the return value format (numeric lamports vs decimal SOL) and does not reconcile the empty input schema with the required ?address=. An agent has enough to attempt the call but not to interpret the result confidently.

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 description is the only source stating that an address must be supplied and that it goes as a query parameter (?address=...). That is genuinely additive, though it creates an unexplained mismatch between the empty schema and the required address.

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?

States a specific resource and output: 'SOL balance for any Solana address', which is enough to distinguish it from erc20-balance and tool_sol_tokens (native SOL vs token balances). It does not explicitly name those siblings as alternatives, so sibling differentiation is inferred rather than stated.

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?

The 'for any Solana address' scope and the ('?address=...') example imply when the tool applies, but there is no explicit guidance on when to prefer it over the sibling balance/token tools, and no note on what happens with invalid or non-Solana addresses.

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