Skip to main content
Glama

Wallet PnL

wallet_pnl
Read-only

Calculate realized and unrealized PnL for a Solana wallet's token trades. Analyzes swap history to compute profit/loss per token in SOL. Costs $0.05 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_pnl"
  }
}

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 useful context beyond them: a concrete per-call price ($0.05 USDC) and the scope limitation that only swap history is analyzed, implying transfers/deposits are excluded. It does not mention latency, history window, or behavior for wallets with no swaps.

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?

Three short sentences, front-loaded with what it does, then the method, then the price. Every sentence carries distinct information with zero filler.

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-only analytic with no output schema, the definition covers purpose, computation basis, unit, and cost. Minor gaps remain around the history window analyzed and what is returned when a wallet has no swap activity.

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 schema coverage is 100%, with the schema documenting the base58 Solana address format. The description adds nothing about the parameter beyond what the schema states, so baseline 3 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?

States a specific verb (calculate) and resource (realized/unrealized PnL for a Solana wallet's token trades), plus the unit (SOL) and data source (swap history). This clearly separates it from siblings like wallet_balance or wallet_profile, though it never names an alternative 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 implied — you call it when you want per-token trading performance for a wallet — and the cost line gives a practical decision signal. But there is no guidance on when to prefer wallet_profile, transaction_parse, or smart_money instead, and no exclusions or prerequisites stated.

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