wallet-tracker

get_signal_history

Read-only

Past signals, for checking whether a kind of signal has worked historically

before acting on a live one.



blockchain: solana, bnb, base, eth or rh

wallet_type: kol, smart or whale (default kol)

days: 7, 30, 90 or "all" (default 30)

mode: cluster, entry or exit. Omit for all modes.

limit: how many signals (default 25)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	How far back to look: 7, 30, 90 or all.	30
`mode`	No	Restrict to cluster, entry or exit. Leave empty for every mode.
`limit`	No	How many entries to return. Keep it small: large results are trimmed to fit the context window anyway.
`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.
`wallet_type`	No	Wallet type. kol is a Key Opinion Leader, an influencer whose calls move markets. smart is a wallet selected for its track record. whale is a large holder, Solana only.	kol

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.4/5.0

Behavior4/5

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

The description adds behavioral context beyond annotations, such as limit trimming and wallet type meanings. It does not contradict the readOnlyHint and openWorldHint annotations, and provides useful details like blockchain-specific wallet availability.

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?

The description is concise and front-loaded with purpose, followed by a clear parameter list. Every sentence adds value with no fluff.

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?

The description covers the purpose, all parameters, and behavioral details like result trimming. With an output schema present, it adequately informs the agent without needing to describe return fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds significant value by explaining wallet type definitions (kol, smart, whale) and blockchain-specific notes (e.g., Rh is Ethereum L2). This goes beyond the schema descriptions.

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 the tool's purpose: 'Past signals, for checking whether a kind of signal has worked historically before acting on a live one.' It uses a specific verb-resource and explicitly mentions the use case, distinguishing it from siblings like get_signals (current signals) and get_analytics.

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 provides clear context for historical validation, implying it should be used before acting on a live signal. However, it does not explicitly say when not to use it or name alternatives, leaving some inference to the agent.

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?