Skip to main content
Glama
Sign In
Hexagon MCP

Hexagon MCP

by smallware-co
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

reddit_demand

Find recommendation and buying-intent Reddit threads for a product category in named subreddits to gauge demand by discussion volume.

Instructions

Find recommendation and buying-intent threads for a product category in the subreddits you name (read-only). A demand proxy for affiliate content. Returns title, score, comment count and age so demand can be judged by discussion volume.

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>",
      "productCategory": "<productCategory>"
    },
    "name": "reddit_demand"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoThreads per subreddit. Default 15.
timeframeNoSearch window. Default: month.
subredditsYesSubreddit names, e.g. ['buildapc','mechanicalkeyboards'].
productCategoryYesWhat to look for, e.g. 'mechanical keyboard' or 'webcam'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and usefully discloses that the tool is read-only and returns title, score, comment count and age. However, it does not mention rate limits, authentication needs, sorting behavior, pagination, or error behavior, leaving meaningful behavioral gaps.

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?

The description is two compact sentences with the core purpose and scope front-loaded. Every sentence adds useful information about read-only behavior, demand-proxy intent, and return fields without waste.

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 read-only search tool with complete parameter schema coverage and no output schema, the description is nearly complete: it explains the purpose, read-only nature, and return fields. The main missing context is explicit differentiation from the sibling reddit_trends tool.

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 all four parameters are already documented in the schema. The description reinforces the roles of subreddits and productCategory but adds no meaning for limit or timeframe beyond the schema, making the baseline score of 3 appropriate.

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?

The description uses a specific verb and resource: 'Find recommendation and buying-intent threads' for a product category in named subreddits. It is clearly not a tautology and communicates the tool's scope, but it does not explicitly differentiate itself from the sibling reddit_trends tool.

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?

It gives implied usage by calling itself 'a demand proxy for affiliate content' and specifying subreddits and product category, but it does not state when to use this tool versus reddit_trends or when not to use it. The guidance is adequate but not explicit.

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