Skip to main content
Glama

Reddit

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • addedInput schema / properties / description
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\")"New value: +"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\"). Accepts task, q, description, search as aliases."
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / task
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "look up FDA drug approvals"
+  },
+  {
+    "query": "analyze housing market trends"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=true and idempotentHint=true. The description adds transparency about return format (top-N, ready-to-call results) and no second lookup needed, which goes beyond basics.

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 front-loaded with purpose and examples, but slightly long. Every sentence adds value, though some redundancy (list of domains could be shortened).

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

Completeness4/5

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

Despite no output schema, the description clearly states what the tool returns (names, descriptions, schemas), which is sufficient for a discovery tool. Context is complete.

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

Parameters4/5

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

Schema coverage is 100%, and the description adds meaning by explaining 'query' with natural language examples and listing aliases (task, q, search, description), clarifying flexibility.

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

Purpose5/5

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

The description uses a specific verb ('Find tools') and resource ('tools'), lists many domains (SEC filings, FDA drugs, etc.), and distinguishes from sibling search tools by being a meta-tool for tool discovery.

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

Usage Guidelines4/5

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

Explicitly states 'Call this FIRST when you have many tools available and want to see the option set', providing clear usage context. Lacks explicit when-not or alternatives, but the context is sufficient.

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

All Reddit toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

The set has several near-duplicate tools: ask_pipeworx and ask_pipeworx_beta are explicitly designed to be identical right now, and ask_pipeworx_grounded, deep_research, and bet_research all overlap on routed data lookup. The three Reddit tools are distinct, but they are dwarfed by a large cluster of unrelated Pipeworx/Polymarket tools, making the actual purpose of the set hard to pin down.

Naming Consistency2/5

Naming conventions are wildly mixed: some tools use verb_noun (get_post, subscribe, suggest_questions), some use noun phrases (entity_profile, recent_alerts, pipeworx_trending), and some use ad-hoc names (ask_pipeworx, bet_research, scan_dependency). Within sub-families (polymarket_*, ask_pipeworx_*) names are consistent, but overall there is no single predictable pattern.

Tool Count1/5

34 tools is excessive for a server named 'Reddit' when only 3 of them (get_post, get_subreddit, search_posts) actually relate to Reddit. The remaining 31 tools cover unrelated domains like Pipeworx data routing, Polymarket betting, memory management, and npm dependency scanning—an extreme scope mismatch for the advertised server name.

Completeness1/5

The Reddit surface is severely incomplete: it offers read-only post/subreddit/search functionality with no create, edit, delete, vote, comment, or user-profile operations. Conversely, the Pipeworx tooling is over-complete relative to the 'Reddit' name, covering data lookups, prediction markets, subscriptions, and memory—none of which belong in a Reddit server.

Resources