Tachyo

marketsummary__get_whale_alerts

[marketsummary] Recent large on-chain moves from the whale feed: which tokens whales are moving, the USD size, and the direction (exchange in or out). Optionally filter by ticker. Free shows the count and the top few (ticker, direction, size); premium unlocks the full board with counterparties via session_token (from verify_wallet_ownership) OR an x402 payment proof. Public whale data. Not financial advice.

Input Schema

TableJSON Schema

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

TDQS

A4.4/5.0

Behavior4/5

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

The description indicates the tool returns public whale data and is read-only ('Public whale data' implies no side effects). It explains the data is not financial advice and mentions different access tiers. Without annotations, it adequately covers behavioral expectations.

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 front-loaded with the core purpose and provides necessary detail without being overly verbose. Every sentence adds value, though it could be slightly more concise. The structure is clear and scannable.

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 tool's purpose, parameters, usage hints (free vs. premium), and behavioral context. It does not detail the exact return format, but given no output schema, this is acceptable for a list-oriented tool. Overall, it provides sufficient context for an AI agent to correctly invoke the tool.

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?

The input schema has three parameters with no descriptions. The tool description adds meaning to all: 'ticker' is explained as optional filter, 'session_token' and 'payment' are described as authentication methods for premium data. This fully compensates for the 0% schema coverage.

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 retrieves recent large on-chain moves from the whale feed, specifying what data is returned (tokens, USD size, direction). It distinguishes itself from sibling tools by focusing on whale alerts rather than general market summaries or other metrics.

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 explains optional filtering by ticker and the two authentication methods (session_token or payment) for premium access. It provides context on free vs. premium usage, but does not explicitly state when not to use this tool or suggest alternative tools for different purposes.

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?