Tokens with the most Zipp coverage in a recent time window — useful for 'what coins is the market talking about right now?' Ordered by mention count desc, then recency. Window defaults to the last 24 hours and is clamped to 1–168h (1h–7d).
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | en-US | |
| limit | No | ||
| window_hours | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses ordering (by mention count descending then recency), window defaults (24 hours), and clamping (1-168 hours). This is good behavioral transparency for a read-only tool, though it omits details like authentication 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences long, front-loads the core purpose, and includes necessary details without extraneous text. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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, ordering, and window behavior. An output schema exists, so return values need not be described. However, the limit parameter and pagination behavior are not addressed, which is a minor gap for a list tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%. The description adds meaning for window_hours (defaults and clamping) but does not describe lang or limit parameters. This partial coverage is adequate but leaves two parameters unexplained, which could confuse an AI agent.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly identifies the tool's purpose: retrieving tokens with the most Zipp coverage in a recent time window. It uses specific verbs ('get') and resources ('trending tokens'), and differentiates from siblings by focusing on 'what coins is the market talking about right now' rather than news or posts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description provides clear usage context: 'useful for what coins is the market talking about right now?' and explains ordering and window constraints. It does not explicitly state when not to use or name alternatives, but the context is sufficient for typical use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct content type or operation (e.g., breaking news vs. latest news, digests vs. guides, token snapshots vs. rankings). Descriptions clearly differentiate purposes, so an agent can easily select the correct tool.
All tools use snake_case with a verb_noun pattern, primarily 'get_*'. The exceptions are 'list_categories' and 'search', which are still clear but break the 'get_' prefix consistency.
With 13 tools, the server covers a broad but focused set of crypto news, education, and market data operations. The number feels appropriate for the domain—not too few to be incomplete, not too many to be overwhelming.
The tool surface provides comprehensive read-only access to news (latest, breaking, featured), editor digests, learn guides, token snapshots, rankings, trending tokens, and search. There are no obvious missing operations for consuming crypto content.
