Tachyo

marketsummary__find_setups

[marketsummary] Screen for trade setups, ranked from OUR computed signals (no hallucinated ranking).

intent: 'fade' = weak coins that just pumped on a catalyst (ride-the-fade / short-the-bounce) / 'momentum' = coins holding strength to ride. Each setup carries pump % (1d/7d), strength vs BTC, a weakness score, mention velocity, the catalyst section, a data-quality flag, and a plain-English reason. Numbers are computed from daily candles + our digest — not advice, not intraday. Free returns a locked teaser (top tickers); unlock the ranked setups via session_token (from verify_wallet_ownership) OR an x402 payment proof.

Input Schema

TableJSON Schema

Name	Required	Default
`intent`	No	fade
`payment`	No
`session_token`	No

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses the data source (daily candles + digest), the nature (not advice, not intraday), and the paywall behavior. Missing details like error handling or rate limits.

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 well-structured with sections for purpose, intents, output details, data source, and access. Each sentence adds value, though slightly longer than necessary.

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?

Given the complexity (3 params, no output schema, no annotations), the description covers core functionality, intents, output fields, and access tiers. Missing edge cases or error scenarios, but adequate for selection.

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

Parameters3/5

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

Schema coverage is 0%, so description adds meaning: intent parameter is explained, session_token and payment are linked to unlocking. However, payment format (x402) is not elaborated, partially compensating.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool screens for trade setups ranked from computed signals, with two intents (fade and momentum). The purpose is specific and distinct from siblings like find_longs/find_shorts, though not explicitly compared.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the two intent options and access tiers (free vs. paid), guiding usage within the tool. However, it does not specify when to use this tool over siblings like find_longs/find_shorts.

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?