wallet-tracker

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

Name	Required	Description	Default
`address`	Yes	Wallet address. Base58 on Solana, 0x-prefixed hex on the EVM chains.
`blockchain`	Yes	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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.1/5.0

Behavior4/5

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

Annotations indicate readOnly and openWorld, which the description complements by specifying it returns realized PnL across tracked history. This adds behavioral context about the data scope and type, without contradicting annotations.

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 short and front-loaded with purpose, but it includes a redundant parameter listing that could be omitted. Overall efficient with minimal waste.

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?

Given the presence of an output schema and annotations, the description adequately covers the tool's behavior (daily/monthly PnL, streak spotting). It could mention time range defaults or pagination, but the context is sufficient for selection.

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% with detailed parameter descriptions. The description only lists blockchain and address without adding extra nuance, so it provides no additional meaning beyond the schema, earning a baseline 3.

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 clearly states it provides daily and monthly realized PnL for a wallet, with explicit use cases for profit/loss and streak spotting. It distinguishes itself by focusing on calendar-based PnL, which is unique among sibling tools.

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?

The description explicitly says 'Use for when a wallet made or lost money, and for spotting streaks,' providing clear context. It lacks explicit when-not-to-use or alternative tool mentions, but the context is sufficient.

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

All wallet-tracker tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct function—comparing tokens vs. wallets, detecting bundles, retrieving historical vs. current signals, etc. Overlap is minimal, and descriptions clearly differentiate similar-sounding tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (compare_, detect_, get_, list_, lookup_), all in snake_case, making it easy to predict and understand the purpose of each tool.

Tool Count4/5

With 21 tools, the set is slightly above the typical 'well-scoped' range, but the breadth of functionality—covering wallet stats, tokens, signals, bundles, and comparisons across multiple blockchains—warrants the number. No tool feels redundant.

Completeness5/5

The tool surface covers essentially all aspects of wallet tracking: browsing, per-wallet stats/history/holdings/connections, token-level analysis, signals, bundles, leaderboards, and activity metrics. No obvious gaps for the stated purpose.

Resources

Need Help?