Skip to main content
Glama
Sign In

Agentery

by com.agentery
OverviewDiscussionsAdmin

Find market gaps

market_gaps
Read-only

Finds jobs callers ask for that few paid products serve: requests seen on this MCP server, clustered by meaning, that sit far from any paid provider. Use this when a seller or investor asks where under-served opportunities are. Returns the request phrasing, distinct_callers, raw_requests, the nearest paid provider and its similarity (low = under-served). headline = jobs asked by two or more callers; weak_leads = one caller; information_requests = questions about a named product. These are research leads from limited traffic, not buyer counts or proof of a market-wide gap; few or none is normal while volume is low. Marked test traffic is excluded. No arguments needed. Use demand_signals instead when you want searches that returned no or only weak results.

Input Schema

NameRequiredDescriptionDefault
rankNogaps (default): whitespace with money, crowded excluded. hot: most active by market pulse, crowding ignored.
limitNoMax gaps (1-50, default 15)
sectorNoOptional sector filter, e.g. 'legal', 'healthcare'
include_ownNoAlso list leads asked ONLY by you (default false: one caller's repeated searches are not independent demand; they are counted in your_own_only_excluded)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "JSON result; identical to the text content block.",
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / include_own
      Added value: +{
+  "description": "Also list leads asked ONLY by you (default false: one caller's repeated searches are not independent demand; they are counted in your_own_only_excluded)",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max niches (1-50, default 15)"New value: +"Max gaps (1-50, default 15)"
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds real context beyond the readOnly/openWorld annotations: test traffic is excluded, small-sample results are normal, and the output is research leads rather than buyer counts or proof of a market-wide gap. The enumeration of returned fields partly duplicates the output schema, but the semantic gloss ('similarity low = under-served', headline = 2+ callers, weak_leads = one caller) is genuinely additive.

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?

Front-loaded with purpose, then routing, then returns, then caveats — a sensible order with no filler sentences. It is dense, though: the return-field list and the lead-tier definitions are packed into one long block, and the caveat about small samples is easy to skim past at the end.

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?

An output schema exists, so return values needn't be re-explained, and the description still covers the interpretive caveats an agent needs to avoid overclaiming. The one material omission is any hint that results can be re-ranked by 'hot' or narrowed by sector, which changes what the tool produces.

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 coverage is 100% and each parameter is well described, so the baseline is 3. The description's only parameter-adjacent statement is 'No arguments needed', which understates the available controls — the rank enum (gaps vs hot) and the sector filter materially change results but are not mentioned or cross-referenced.

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?

Specific verb plus a precisely scoped resource: 'jobs callers ask for that few paid products serve ... clustered by meaning, that sit far from any paid provider.' It also names the sibling it is not (demand_signals) and the audience that asks for it, so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('when a seller or investor asks where under-served opportunities are') and an explicit alternative with its own condition ('Use demand_signals instead when you want searches that returned no or only weak results'). This is the when/when-not/alternative pattern at full strength.

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

All Agentery toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources