threadr-mcp

get_trending_subreddits

Retrieve currently popular subreddits to identify trending Reddit communities and topics. Use it to discover where discussions are happening now.

Instructions

Get currently popular subreddits

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_trending_subreddits"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Sep 13, 2026

TDQS

C2.6/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description must carry the full behavioral burden. 'Get' implies a read-only operation, but the description does not disclose what 'popular' means (e.g., time window, ranking algorithm), return format, rate limits, or that it is safe/read-only. This is insufficient for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence with no wasted words, and the core purpose is front-loaded. However, it is arguably too terse for a tool that needs more context, but from a pure conciseness standpoint it is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with one parameter, no output schema, and no annotations, the description provides minimal context. It omits parameter usage, return format, and any behavioral details, leaving the agent to infer too much.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description does not mention the single 'limit' parameter at all. While the schema defines type, default, min, and max, the description adds no semantic meaning about what limit controls or how to use it. This fails to compensate for the lack of schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb 'Get' and resource 'currently popular subreddits', which is clear and distinct from sibling tools that focus on specific subreddits, posts, or users. However, it does not explicitly differentiate from any sibling by naming an alternative or scope boundary, so it falls short of the 5 criteria.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like get_subreddit_info or search_posts. It also does not state prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server