Skip to main content
Glama

Find where people ask for what a business sells

find_people_asking
Read-only

The real places (subreddits, forums, communities, directories) where the buyers of a business already ask for something like it, each with why, the move to make there, a source URL when live search opened it, and a read on whether posting or commenting is allowed. Three places without an account; a free plan holds the rest and the live threads. Input: the business in a sentence or two, or its website URL.

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": {
      "business": "<business>"
    },
    "name": "find_people_asking"
  }
}

Input Schema

NameRequiredDescriptionDefault
businessYesWhat the business sells and to whom, or its URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, destructiveHint=false, openWorldHint=true, idempotentHint=false), so the bar is lower; the description still adds meaningful behavior beyond them — that results are capped at three places without an account and that a free plan gates the remainder and the live threads. The 'source URL when live search opened it' note clarifies why some entries lack URLs, which is genuinely useful. Missing only rate/latency or freshness details.

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?

Two sentences, front-loaded with what the tool finds and followed by the result fields and account limits. The parenthetical list and run-on clause ('each with why, the move to make there...') are dense but every element earns its place by describing a return field.

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?

There is no output schema, so the description must carry the return shape — and it does, naming the reasoning, recommended action, source URL, and posting-permission signal per place. Combined with the free-tier cap and accepted input forms, an agent has enough to call this correctly; only search scope/recency is unaddressed.

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?

With a single required parameter and 100% schema description coverage, the schema already carries the semantics. The description's 'the business in a sentence or two, or its website URL' largely restates the schema's own wording, adding no new constraints, examples, or failure modes for that input.

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 identifies a specific resource — subreddits, forums, communities and directories where a business's buyers already ask for something similar — and enumerates what each result contains (why, the move, source URL, posting permission). It is clear what the tool produces, though it never states the action verb outright and does not distinguish itself by name from siblings like validate_idea or check_subreddit_rules.

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?

Usage is only implied: an agent can infer this is a prospecting/community-discovery step before drafting or validating, but the description never says when to reach for it versus validate_idea or check_subreddit_rules, nor any preconditions. The closing 'Input:' line is parameter guidance rather than when-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources