wallet_historyWallet portfolio over time: snapshots with position changes (added/removed holdings) and direction indicators.
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | Solana wallet address (base58) | |
| lookback | No | Lookback period | 7d |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description provides useful context about the output content (snapshots, position changes, direction indicators) but discloses no behavioral traits such as read-only nature, rate limits, or data granularity. With no annotations provided, the description carries the full burden and partially meets it by indicating the historical/read-oriented nature, but lacks deeper transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that immediately conveys the core functionality and adds relevant detail about snapshots, position changes, and direction indicators. Every word earns its place, and the structure is clean.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read tool with a complete parameter schema, the description offers a basic understanding of the output. However, without an output schema or annotations, it lacks details on response format, error scenarios, and how it differs from similar tools like portfolio_history, making it only minimally complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already has 100% coverage with descriptions for both parameters (address and lookback). The description does not add any parameter-specific meaning beyond what the schema provides, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states what the tool does: shows wallet portfolio over time with snapshots, position changes, and direction indicators. The verb is implied ('get history'), and the resource is specific. However, it does not distinguish from the sibling tool 'portfolio_history', which likely serves a similar purpose, so it misses the differentiation needed for a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives. The description is purely declarative and does not mention exclusions, alternatives, or specific use cases. With many sibling tools like portfolio_history and wallet_graph, the lack of any usage direction leaves the agent to guess.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
With 32 tools, several have overlapping purposes, such as wallet_history vs portfolio_history (both track wallet portfolio over time) and smart_money_flow vs smart_money_trenches (both follow smart money movements). However, most tools have clearly distinct scopes, and detailed descriptions help differentiate them.
All tool names follow snake_case with a predictable verb_noun or noun phrase pattern (e.g., enrich_token, compare_wallets, perps_market_trend). The consistent structure makes the set easy to navigate, even the 'perps_' prefix group is uniform.
32 tools is well above the 25-tool threshold, making the surface feel heavy. While the breadth reflects the wide domain of Solana analytics, the sheer number can overwhelm agents and increase the chance of selecting the wrong tool.
The tool set covers most aspects of Solana token/wallet/perp analysis, including enrichment, comparison, trend tracking, smart money flows, and perp market structure. Minor gaps exist, such as no direct historical OHLCV endpoint, but the existing tools handle core workflows well.