Skip to main content
Glama

wallet-tracker

by xyz.cabalspy
OverviewDiscussionsAdmin

get_pnl_calendar

Read-only
Daily and monthly realized profit and loss for a wallet across its tracked
history. Use for when a wallet made or lost money, and for spotting streaks.

blockchain: solana, bnb, base, eth or rh
address: the wallet address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesWallet address. Base58 on Solana, 0x-prefixed hex on the EVM chains.
blockchainYesBlockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base and rh have kol and smart; eth has kol only. rh is Robinhood Chain, an Ethereum L2.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Wallet address. Base58 on Solana, 0x-prefixed hex on the EVM chains."
    • addedInput schema / properties / blockchain / description
      Added value: +"Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base and rh have kol and smart; eth has kol only. rh is Robinhood Chain, an Ethereum L2."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "get_pnl_calendarDictOutput",
+  "type": "object"
+}
  2. Changed5 schema fields changed
    • removedInput schema / properties / address / description
      Removed value: -"Wallet address (Solana base58 or 0x… for EVM chains)."
    • removedInput schema / properties / address / examples
      Removed value: -[
-  "G6fUXjMKPJzCY1rveAE6Qm7wy5U3vZgKDJmN1VPAdiZC"
-]
    • removedInput schema / properties / blockchain / description
      Removed value: -"Blockchain network: solana, bnb, base or eth."
    • removedInput schema / properties / blockchain / examples
      Removed value: -[
-  "solana"
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "get_pnl_calendarDictOutput",
-  "type": "object"
-}New value: +null
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only cover read-only/open-world, so the description usefully adds that the metric is *realized* (not unrealized), that granularity is daily and monthly, and that history is scoped to the wallet's tracked range. It omits auth, rate limits and pagination, but adds real context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is front-loaded and tight, but the two trailing lines that re-list blockchain values and describe the address merely duplicate schema content that is already fully documented.

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?

With an output schema present, return values need not be explained, and the description adequately conveys what the tool produces and when to reach for it for a simple two-parameter read tool. Only the absence of any alternative routing keeps it from a 5.

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 description coverage is 100% and the schema defines both parameters in more detail than the description (including chain-specific wallet-type and Base58 vs 0x addressing rules). The description's restatement of the blockchain list and address adds nothing new, 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?

The description names a specific metric and resource: daily and monthly realized PnL for a wallet over its tracked history. That is clearly distinct from siblings like get_token_stats or get_wallet_history, though no sibling is named 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?

"Use for when a wallet made or lost money, and for spotting streaks" gives a genuine use case, but there is no when-not guidance and no alternative tool named for related PnL or performance questions.

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

All wallet-tracker toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources