Skip to main content
Glama

Tachyo

by ai.tachyo.mcp

marketsummary__get_digest

[marketsummary] The paid Degen Digest — actionable calls with contract addresses, grouped by section.

section: HOT / SIGNALS / WARNINGS / all. asset_class: crypto / equity / all. ticker: optional symbol filter (e.g. HYPE). timeframe: 6h / 24h / 7d / 30d / 90d. The digest is premium — free returns a locked teaser. Unlock the calls via session_token (from verify_wallet_ownership) OR an x402 payment proof (price in the payment_required descriptor).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoen
tickerNo
paymentNo
sectionNoall
timeframeNo24h
asset_classNoall
session_tokenNo

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the premium nature, locking behavior, and authentication options, but does not mention error handling, rate limits, or output format, leaving some behavioral gaps.

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 about 100 words, front-loaded with the purpose, and efficiently lists parameter options in a readable format. It is concise without being overly brief, earning its sentences.

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?

Given no annotations, no output schema, and 7 params with 0% schema coverage, the description covers purpose, parameters, and payment but lacks output description, error scenarios, and detailed authentication flow. It is adequate but not fully comprehensive.

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?

With 0% schema description coverage, the description adds meaning for 6 of 7 parameters (section, asset_class, ticker, timeframe, payment, session_token), explaining their values and purposes. Only 'lang' is omitted, which has a clear default.

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 it provides the 'paid Degen Digest' with actionable calls and contract addresses, grouped by section. It lists the filtering parameters, distinguishing it from sibling tools that offer different summary types.

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 that free use returns a locked teaser, and unlocking requires a session_token or x402 payment proof, providing clear guidance on when to use and how to access full content. It does not explicitly compare to alternatives but the context is sufficient.

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

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