Skip to main content
Glama
Sign In
Hexagon MCP

Hexagon MCP

by smallware-co
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

reddit_trends

Find rising posts in specified subreddits to see what is gaining traction right now; returns each post's title, score, comment count, and age.

Instructions

Rising posts from the subreddits you name (read-only), a 'what is gaining traction right now in my niche' signal. Returns title, score, comment count and age per post.

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": {
      "subreddits": "<subreddits>"
    },
    "name": "reddit_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPosts per subreddit. Default 10.
subredditsYesSubreddit names, e.g. ['pcgaming','buildapc'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description correctly discloses that the tool is read-only and lists the returned fields. However, it leaves out important behavioral context such as how 'rising' is determined, the time window, rate limits, or ordering.

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

Conciseness5/5

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

Two tightly written sentences with the core purpose front-loaded and no wasted words. The return-value summary is brief and useful.

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?

For a simple two-parameter read-only tool, the description covers purpose, scope, read-only nature, and return contents. The only notable gap is not clarifying how 'rising' posts are selected or over what timeframe.

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 description coverage is 100%, so the parameters are already well documented, including the limit default and subreddit examples. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource ('rising posts from the subreddits you name') and frames the signal as 'what is gaining traction right now in my niche.' This differentiates it from siblings like reddit_demand without needing to name them.

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 phrase 'what is gaining traction right now in my niche' implies when the tool is useful, but there is no explicit when-to-use versus when-not-to-use guidance and no mention of alternatives such as reddit_demand.

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

Deploy Server

Other Tools