get_subreddit_topSubreddit Posts > Top Group: Subreddit Posts. Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| t | No | ||
| show | No | ||
| after | No | ||
| count | No | ||
| limit | No | ||
| before | No | ||
| sr_detail | No | ||
| subreddit | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description provides no behavioral transparency at all. It only mentions billing cost ('Billing per call: 1 Credits'), which is a minor operational detail but does not disclose whether this is a read operation, what side effects might occur, or any limitations. With no annotations, the description carries the full burden, and it fails to convey that this is a safe read-like operation.
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 extremely short (one sentence plus billing line), which is concise in word count but under-specifies. It is front-loaded with the title, but the content is nearly useless. This is under-specification, not effective conciseness.
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 complexity (8 parameters, no annotations, no output schema, and many sibling tools), the description is grossly inadequate. It does nothing to help the agent understand the tool's purpose, parameters, or how it differs from similar tools like get_top or get_subreddit_posts.
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%, so the description must compensate for the 8 parameters, but it provides zero parameter details. The schema itself has no descriptions or enums, leaving all parameters ambiguous. The description adds no value in explaining what 't', 'show', 'after', 'before', 'sr_detail', etc., mean. This is a significant gap.
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 is essentially a tautological restatement of the title and name ('Subreddit Posts > Top Group: Subreddit Posts.'), providing no additional information. It fails to state what the tool does beyond the implied 'get top posts from a subreddit,' which is inferred from the name and sibling tools. This is a low but not completely missing purpose clarity.
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?
No usage guidance is provided in the description. There is no mention of when to use this tool versus alternatives like get_subreddit_hot or get_subreddit_new, nor any prerequisites or context. The agent must infer from the name that it retrieves top posts, but there is no explicit guidance.
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 resource and action combination (e.g., get_hot vs get_subreddit_hot vs get_user_posts). The scope is clearly delineated by prefixes like 'get_subreddit' and 'get_user', making it easy for an agent to pick the right tool.
All tools follow the consistent 'get_<resource>_<modifier>' pattern using snake_case. Even get_by_id fits the general get_ prefix style. The naming is uniform and predictable across 31 tools.
With 31 tools, the count exceeds the 25+ threshold considered too many. While Reddit has many read endpoints, this server covers only GET operations and still feels bloated, especially with multiple near-duplicate sort variants. It could be consolidated.
The tool surface is entirely read-only (only get_* operations). For a Reddit integration, obvious write operations like posting, commenting, voting, and moderation actions are missing. This creates significant gaps for many use cases and limits the server to exploration only.