Skip to main content
Glama

YRUZ Wallet Balance (0.002 USDC)

wallet_balance
Read-onlyIdempotent

USDC and gas balance of any Solana or Base address, read from the chain: USDC amount, SOL or ETH for fees, whether the USDC account exists, and whether the wallet can pay a given x402 price. Lets an agent check its own funds or a counterparty before it pays. Price: 0.002 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"wallet_balance"}. Same tool over HTTP: https://yruz.one/api/wallet?address=CWfaj5vDppWCp4q1X4iPYGWpCGY2Rerj9DQWqxTnz1Pp

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

Input Schema

NameRequiredDescriptionDefault
amountNooptional USDC price to test, e.g. 0.01
addressYesSolana (base58) or Base (0x) address (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / address / examples
      Added value: +[
      +  "CWfaj5vDppWCp4q1X4iPYGWpCGY2Rerj9DQWqxTnz1Pp"
      +]
    • addedInput schema / properties / address / pattern
      Added value: +"^(0x[0-9a-fA-F]{40}|[1-9A-HJ-NP-Za-km-z]{32,44})$"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations by disclosing the x402 payment flow: cost per call, no account or API key required, no charge on invalid input or failed runs, and a PaymentRequired response without payment. This is exactly the behavioral context an agent needs before invoking a paid tool.

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-loads the purpose, then payment terms, then invocation help, so it is easy to scan. It is slightly long with the full HTTP URL and get_example pointer, but each element serves a real need for a paid remote tool.

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?

With no output schema, the description compensates by enumerating every returned field (balance, fee token, account existence, affordability check). Combined with annotations and full schema coverage, an agent has everything needed to call it correctly and understand the payment consequences.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that 'amount' tests 'whether the wallet can pay a given x402 price' — clarifying the parameter's role in the output rather than just restating 'optional USDC price to test.'

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 ('USDC and gas balance ... read from the chain') and scopes it to Solana or Base addresses. It enumerates exactly what is returned (USDC amount, SOL/ETH for fees, account existence, x402 affordability), which distinguishes it from portfolio-style siblings like solana_portfolio.

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?

Explicitly frames the use case: 'check its own funds or a counterparty before it pays.' The payment preconditions (invalid input refused before payment, failed run never charged) give clear context for when a call will and won't cost. It does not name an alternative tool, so it falls short of a 5.

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.