Skip to main content
Glama

Verity Analytics

scan_niche_demand

Scan YouTube, Reddit, and Hacker News to compute live content demand gap scores and Views-Per-Hour (VPH) outliers. Free accounts include 5 total MCP scans per year within a 30-day evaluation window.

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": {
      "niche": "<niche>"
    },
    "name": "scan_niche_demand"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheYesTarget content niche or topic query (e.g., "AI coding agents").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description bears full disclosure duty; it does disclose the data sources, that scoring is 'live,' and an unusual hard quota (5 scans/year for free accounts over a 30-day window), which is genuinely useful planning context. It does not say whether the scan is read-only/cached, how long it takes, or what a scan consumes beyond the free-tier limit.

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 tight sentences, with the core action and sources front-loaded and the quota caveat second. Nothing is padded, though the quota sentence could name the consequence of exceeding it.

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?

For a multi-source scan with no output schema and no annotations, the description should sketch what comes back (score fields, outlier lists) and any cost/latency behavior. It partially does via 'demand gap scores and VPH outliers' but leaves the return shape and per-scan cost implications implicit.

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?

Only one parameter exists and the schema already documents it at 100% coverage with an example ('AI coding agents'), so the baseline is 3. The description adds no extra meaning about the niche string—no guidance on breadth, aliases, or how broad vs. narrow phrasing affects the scan.

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 names a specific verb ('Scan') and concrete resources (YouTube, Reddit, Hacker News) plus the computed artifacts (content demand gap scores and VPH outliers). That is enough to separate it from predict_hook_retention and synthesize_omnichannel_assets, though it never explicitly contrasts itself with them.

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

Usage Guidelines2/5

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

There is no statement of when to reach for this scan versus the sibling tools, and no prerequisites or exclusions. The quota sentence ('5 total MCP scans per year within a 30-day evaluation window') is a constraint, not selection guidance, so the agent is left to infer the use case from the purpose sentence alone.

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