Subreddit Rules
get_subreddit_rulesSubreddit Rules Group: Subreddit. Billing per call: 1 Credits.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| subreddit | No |
get_subreddit_rulesSubreddit Rules Group: Subreddit. Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| 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?
With no annotations provided, the description carries the full burden of disclosing behavior, but it only mentions billing. It does not indicate whether the operation is read-only, what inputs affect results, or what the output might look like. This is a complete lack of behavioral transparency.
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, but this is under-specification rather than effective conciseness. Every word is either redundant with the title or irrelevant to tool usage (billing), so the structure provides no actionable 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?
Given the lack of annotations, output schema, and parameter documentation, the description needed to explain the tool's function and context. It is completely inadequate for an agent to select or invoke this tool correctly, especially alongside many similar subreddit-related tools.
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 input schema has a single parameter 'subreddit' with 0% schema description coverage, and the description does not explain the parameter's meaning or format. The description adds no semantic value beyond the bare schema property name, leaving the agent without guidance on what value to provide.
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 'Subreddit Rules Group: Subreddit. Billing per call: 1 Credits.' merely restates the tool name and title, providing no verb or clear action. It fails to say that the tool retrieves subreddit rules, making it a tautology rather than a purpose statement.
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?
There is no guidance on when to use this tool or how it differs from sibling tools. The only non-name information is billing cost, which does not help with usage decisions. No alternatives or exclusions are mentioned.
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.