[News & Media] Get top stories from Hacker News (Y Combinator). Returns titles, URLs, scores, and comment counts. Great for tech and startup news.
Args: max_results: Maximum number of stories to return (default 20)
| Name | Required | Description | Default |
|---|---|---|---|
| max_results | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations (readOnlyHint=true, openWorldHint=true) already indicate a safe read operation. The description adds that it returns top stories with specific fields (titles, URLs, scores, comment counts), which is consistent and informative. No contradiction.
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 front-loaded with purpose, then return details, usage context, and parameter. Every sentence is valuable with no fluff.
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?
Given the tool's simplicity (1 parameter, no output schema), the description covers purpose, return fields, and parameter. It lacks explicit details on output format (e.g., JSON structure), but the listed fields are sufficient for a list result.
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?
The description covers the sole parameter 'max_results' with an explanation: 'Maximum number of stories to return (default 20).' Since schema description coverage is 0%, this fully compensates and adds clear meaning beyond the schema's type/default.
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 states 'Get top stories from Hacker News (Y Combinator)' with a specific verb and resource, and lists return fields (titles, URLs, scores, comment counts). It distinguishes itself from sibling news tools like news__get_ap_news or news__get_bbc_news by explicitly naming Hacker News.
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?
The note 'Great for tech and startup news' provides usage context. While it does not explicitly state when not to use it or name alternatives, the context is clear enough given the tool name and sibling list.
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.
Many tools have overlapping functionality across categories (e.g., multiple search_arxiv, search_google_scholar, real estate tools, DNS/WHOIS checks). An agent would struggle to differentiate between similar tools from different categories, leading to ambiguity.
Tools follow a 'category__verb_noun' pattern mostly, but verbs vary (get, search, screen, check, etc.) and some categories use different orders (e.g., 'get_repo_stats' vs 'search_repos'). The consistency is acceptable but not uniform across the entire set.
With 152 tools, the server is excessively large for a single MCP server. While it aims to be an all-in-one gateway, the sheer number overwhelms the agent and likely exceeds practical limits for coherent selection.
The server covers a wide range of domains (finance, real estate, news, developer tools, etc.) but has notable gaps (e.g., social media APIs, CRM tools). Coverage is broad but not exhaustive, and some niche areas (e.g., global stock exchanges) are over-represented.