Editor-picked feature stories (is_featured=TRUE). No time window. Use when the user wants curated highlights rather than recency-sorted news.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | en-US | |
| limit | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses 'No time window' as a behavioral trait. No annotations exist, so description carries full burden. It could mention caching or pagination, but given tool simplicity, this is adequate.
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?
Two sentences, front-loaded with key information, no waste. Every sentence earns its place.
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?
Covers purpose and usage well, but misses parameter details. With output schema present, return values are covered. A slightly more complete description would mention parameter effects.
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%, but the description fails to explain the 'lang' and 'limit' parameters. For a low-coverage scenario, the description should compensate, but it does not.
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?
The description clearly states the tool retrieves editor-picked feature stories and distinguishes from recency-sorted news by noting 'No time window.' This separates it from siblings like get_latest.
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?
Explicitly says 'Use when the user wants curated highlights rather than recency-sorted news,' providing clear guidance on when to use and implying alternative tools.
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.
