Tachyo

marketsummary__find_shorts

[marketsummary] Short candidates — coins with a BEARISH catalyst (the real short signal, which the momentum-based setups miss). A coin need not have pumped: a foundation moving funds to an exchange, or a DATED token unlock, is a fundamental sell catalyst. Each candidate carries the catalyst type (unlock / insider distribution / exchange inflow /...), a dated-unlock flag with the date when known, and the evidence. Free = count + how many are dated + top 3 tickers; premium = the full ranked list. Liquidity and borrow are on you — microcaps can squeeze. Not financial advice.

Input Schema

TableJSON Schema

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

TDQS

A4.1/5.0

Behavior5/5

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

Discloses limitations (liquidity and borrow on user, microcaps can squeeze) and includes a disclaimer. With no annotations, this is comprehensive for a read-only tool.

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?

Well-structured and informative, but could be slightly more concise. Front-loads the core purpose.

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

Completeness3/5

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

Covers tool function and limitations well, but lacks parameter documentation, which is a gap given no schema descriptions and no output schema.

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

Parameters2/5

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

Does not explain the input parameters (payment, window_days, session_token) despite 0% schema description coverage. Only hints at payment affecting free vs premium.

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?

Clearly states the tool finds short candidates with bearish catalysts, distinguishes from momentum-based setups, and lists specific catalyst types (unlock, insider distribution, exchange inflow).

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?

Provides guidance on free vs premium tiers, but does not explicitly state when to use this tool instead of siblings like find_longs or find_setups, though it hints at different signal types.

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?