Tachyo

marketsummary__get_smart_money_flow

[marketsummary] Which tickers are smart-money / KOL wallets net-buying right now? A de-identified market-wide net-USD accumulation feed (no wallets, no addresses, no tags). window_hours: 6 / 12 / 24 / 48. Free = the top few tickers + direction; premium unlocks the full board (net USD, distinct-wallet counts, full-position opens, pre-catalyst flags) via session_token (from verify_wallet_ownership) OR an x402 payment proof. Signal is UNVALIDATED (pending point-in-time validation). Not financial advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`payment`	No
`window_hours`	No
`session_token`	No

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries full burden and is transparent: it discloses de-identification, free vs premium tiers, authentication requirements, valid window_hours values, and notes that the signal is unvalidated and not financial advice.

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 a dense single paragraph but conveys all necessary information efficiently. A bit more structure (e.g., bullet points) could improve scannability, but it is reasonably concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description explains what the output contains (top tickers + direction for free; full board with net USD, wallet counts, etc. for premium). It covers all parameters, usage context, and limitations, making it complete for an agent to decide and invoke correctly.

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

Parameters5/5

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

Schema descriptions are absent (0% coverage), but the description adds meaning for all three parameters: window_hours options (6/12/24/48), session_token source (verify_wallet_ownership), and payment as x402 proof. It explains free vs premium functionality tied to these parameters.

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 a list of tickers being net-bought by smart money/KOL wallets, a de-identified market-wide net-USD accumulation feed. It distinguishes from siblings by focusing on smart money flow, not general trends or whale alerts.

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?

It explains free vs premium access and required authentication (session_token or payment). It does not explicitly list when not to use it or compare to siblings, but the context from sibling names provides alternatives.

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

All Tachyo 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

A3.8/5.0

Disambiguation5/5

Each tool targets a distinct aspect of market analysis or token safety, with clear descriptions that avoid overlap. Tools like find_longs and find_shorts are opposites, and other get_* tools each address unique metrics (e.g., buzz, attention shifts, smart money flow). No two tools have ambiguous boundaries.

Naming Consistency4/5

Tools are prefixed by category (marketsummary__, tokensafety__, verify__), and most use a verb_noun pattern (e.g., get_liquidity, find_longs). However, there is some variation: 'ask_market', 'track_narrative', and longer names like 'attention_vs_price_divergence' break the pure 'get_' pattern. Overall, the naming is logical and predictable.

Tool Count5/5

With 24 tools, the server covers a wide range of crypto market analysis, from general summaries to specific signals (e.g., conviction gap, smart money flow) and token safety. The count is well-scoped for the domain; each tool serves a clear purpose without being excessive.

Completeness5/5

The tool set is comprehensive for a market analysis server: it includes natural language querying, trend detection, sentiment, liquidity, whale activity, safety checks, and wallet verification for premium access. Missing trading actions are outside the stated purpose, so no gaps are apparent.

Resources

Need Help?