Skip to main content
Glama

find_subreddits

Read-onlyIdempotent

Find subreddits by topic or name prefix, querying live Reddit when a session is configured and falling back to the Arctic Shift archive for reliable discovery.

Instructions

Find subreddits by topic (live) or by name prefix (archive).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "find_subreddits"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesTopic (live) or name prefix (archive)
sourceNoData source. 'auto' tries live reddit.com (if a session cookie is configured) and falls back to the Arctic Shift archive; 'live' or 'archive' forces one.auto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and idempotence are covered. The only behavioral detail added is the live-vs-archive split, which is essentially a restatement of the `source` parameter's schema description. Nothing is said about network failure modes, rate limits, or result ordering.

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?

A single front-loaded sentence with zero filler; the mode distinction is stated immediately. It is efficient but so compressed that useful context was omitted rather than trimmed.

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

Completeness3/5

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

With three parameters, one enum, no output schema and annotations covering the safety profile, the description is minimally adequate. It does not indicate what a result looks like, how many are returned by default, or what happens when the live path is unavailable, which an agent would need to plan a call.

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

Parameters3/5

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

Schema coverage is 67%, with `limit` undocumented in the schema, yet the description never mentions result count, paging, or what 'auto' fallback means in practice. The mapping of query semantics to source is useful but duplicates the schema's own `query` and `source` descriptions rather than adding meaning.

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 and resource ("Find subreddits") and distinguishes two discovery modes: topic lookup and name-prefix lookup. It is clearly a discovery tool rather than a fetch-one (get_subreddit_info) or content-browsing tool, though it never names a sibling to sharpen that contrast.

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

Usage Guidelines3/5

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

The parenthetical modes imply when each search style applies, but there is no explicit when-to-use vs. when-not guidance and no pointer to alternatives such as get_subreddit_info once a subreddit is already known. Usage is inferred rather than stated.

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