Skip to main content
Glama

Wallet profile

wallet_profile
Read-only

Get a complete wallet profile: SOL balance, all token holdings with USD values, NFT count, and top holdings ranked by value. Costs $0.005 USDC per call.

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": {
      "walletAddress": "<walletAddress>"
    },
    "name": "wallet_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletAddressYesSolana wallet address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely non-obvious context no structured field carries — the $0.005 USDC per-call cost. It also discloses the shape of the payload (balance, holdings with USD valuations, NFT count, ranking) despite there being no output schema.

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?

Two sentences, zero filler. The capability statement leads and the cost caveat follows — exactly the right front-loading for a paid tool.

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 single-parameter read tool with no output schema, the description covers the return contents and the pricing caveat, which is most of what an agent needs. The remaining gap is sibling disambiguation against wallet_balance/wallet_pnl.

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?

Only one parameter and the schema description coverage is 100%, with 'Solana wallet address (base58)' documented in the schema itself. The description adds no parameter meaning at all, so the baseline 3 for high-coverage schemas applies.

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?

Specific verb (get) plus resource (wallet profile), and it enumerates exactly what's returned: SOL balance, token holdings with USD values, NFT count, ranked top holdings. That enumeration implicitly distinguishes it from the narrower wallet_balance sibling, but it never names or contrasts with wallet_balance or wallet_pnl explicitly.

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 — an agent can infer 'use this for a full wallet overview' from the contents list. There is no explicit when-to-use/when-not statement and no routing to wallet_balance (cheaper, balance-only) or wallet_pnl, both of which overlap this tool's scope.

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