Skip to main content
Glama

YRUZ Solana Portfolio (0.005 USDC)

solana_portfolio
Read-onlyIdempotent

Every token a Solana wallet holds, valued in USD: SOL and all fungible SPL and Token-2022 balances with symbol, name, amount, price and value, sorted by value, plus the total portfolio value and the NFT count. One call instead of dozens of RPC reads. Price: 0.005 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":"solana_portfolio"}. Same tool over HTTP: https://yruz.one/api/crypto/portfolio?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": "solana_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesSolana wallet address (required)
min_usdNohide tokens worth less than this, default 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / address / examples
      Added value: +[
      +  "CWfaj5vDppWCp4q1X4iPYGWpCGY2Rerj9DQWqxTnz1Pp"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond annotations, the description discloses critical behavioral traits: the price (0.005 USDC per call via x402), that invalid input is refused before payment, that failed runs are never charged, and that missing payment returns a PaymentRequired response. These details are essential for an agent to understand cost and error handling.

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?

The description is front-loaded with the core purpose and output fields, then follows with payment and calling details. It is slightly longer than necessary due to the full HTTP URL and example call, but every sentence contributes useful information and the structure is logical.

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?

Given the tool’s complexity (blockchain data, payment model) and the absence of an output schema, the description covers the returned fields (symbol, name, amount, price, value, total, NFT count) and payment/error behavior fully. An agent has everything needed to invoke it correctly.

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 coverage is 100%, so the schema already documents both parameters. The description adds output field context ('symbol, name, amount, price and value, sorted by value') but does not clarify the min_usd parameter beyond what the schema provides. Baseline 3 is appropriate when schema does the heavy lifting.

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 states a specific verb and resource: it returns 'Every token a Solana wallet holds, valued in USD,' enumerating SOL, SPL, Token-2022 balances, and total portfolio value plus NFT count. This is clearly distinct from siblings like solana_token_check or wallet_balance, which focus on individual tokens or raw balances rather than a full valued 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?

It gives clear context for when to use the tool ('One call instead of dozens of RPC reads') and explains the payment prerequisite, but it does not explicitly name alternatives or state when not to use it. The reference to get_example for calling details is helpful but not a usage exclusion.

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.