[Reddit] Get posts from a subreddit. Returns titles, scores, comments. Args: subreddit: Subreddit name (e.g. 'technology') sort: Sort order: 'hot', 'new', 'top' (default 'hot') max_results: Max posts (default 25)
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | hot | |
| subreddit | Yes | ||
| max_results | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds return fields but no additional behavioral traits beyond readOnlyHint and openWorldHint annotations. No mention of auth, rate limits, or pagination.
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 concise sentences plus arg list. Front-loaded with purpose, no redundant information.
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?
Adequate for a simple read-only tool, but lacks output schema and might benefit from mentioning list return or limitations.
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 has 0% coverage; description compensates with parameter descriptions, examples, defaults, and enum values. Adds meaning beyond type and 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 posts from a subreddit' with verb and resource, and specifies return values. Distinguishes from sibling reddit__search_reddit which likely searches across reddit.
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?
Implies usage for fetching posts from a single subreddit, but no explicit when-to-use or alternatives. Sibling reddit__search_reddit exists but not compared.
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.