solanaprox-mcp

check_balance

Verify the configured token's USDC balance, today's spend against its cap, expiry, and any deposits waiting to be claimed.

Instructions

Check the configured token's USDC balance, today's spend against its cap, its expiry and any deposits waiting to be claimed (GET /v1/balance). Free.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.0.0Nov 7, 2026

removedInput schema / properties / wallet

Removed value: -{
-  "description": "Solana wallet address to check. Defaults to configured wallet.",
-  "type": "string"
-}

removedInput schema / required
```
Removed value: -[]
```

First observedv1.0.0Mar 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the operation is a GET (implying read-only) and that it is 'Free' (no cost), and 'configured token's' implies authentication. However, it does not mention rate limits, idempotency, or error behavior, leaving key behavioral traits unspecified.

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?

The description is a single, well-structured sentence that front-loads the core purpose and enumerates return items without any unnecessary wording. Every clause earns its place.

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

Completeness4/5

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

For a zero-parameter read-only tool with no output schema and no annotations, the description is largely complete: it states the method, cost, and the specific data returned. It could be improved by clarifying the response structure or distinguishing from sibling tools, but it provides enough context for an agent to understand what the tool does.

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 no parameter semantics to add. The baseline for zero-parameter tools is 4, and the description appropriately does not invent parameter details.

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?

The description uses a specific verb 'Check' with the resource 'balance' and enumerates what is returned: USDC balance, today's spend against cap, expiry, and deposits waiting to be claimed. It clearly states the tool's purpose but does not explicitly differentiate it from sibling tools like deposit_info or get_activity, which may overlap.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The purpose implies a usage context, but the description lacks any routing information that would help an agent choose between check_balance, deposit_info, and get_activity.

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

Deploy Server