Skip to main content
Glama

DDMarketer

by io.github.CodePhantom-1
OverviewDiscussionsAdmin

Search validated SaaS gaps

search_gaps
Read-only

Search validated software opportunities by keyword. Each gap is a real, recurring user complaint scored for commercial intent (willingness to pay). Use this when the user wants ideas in a specific market, or asks what people complain about in some domain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax gaps to return (1-25, default 10).
queryYesKeywords describing the market or problem space, e.g. 'shopify accounting' or 'developer onboarding'.
categoryNoOptional exact category filter, e.g. 'E-commerce', 'DevTools'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
gapsYes
looseNoTrue when no gap matched all your terms and these are loosely related instead. Not validation.
scopeNoget_top_gaps only: 'weekly' = the source complaints are from the last 7 days; 'all-time' = the week was empty, so these are the highest-intent gaps overall.
totalYesExact number of gaps matching the query in the corpus, NOT the length of the list above -- the list is capped by `limit`. Quote this, not gaps.length, when telling the user how much demand there is.
weekOfNoget_top_gaps only, present with scope 'weekly': the UTC date the 7-day window opened (YYYY-MM-DD).
hasMoreYesTrue when more gaps matched than the list carries (the query is limit-clamped). Offer to narrow or paginate rather than implying the list is everything.
dossierUrlYes
upgradeUrlNoPresent only when the caller's plan does not include full dossiers: the page that unlocks them. Surface it when the user wants depth the teaser does not have.
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / limit / default
      Added value: +10
    • addedInput schema / properties / limit / maximum
      Added value: +25
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / query / maxLength
      Added value: +300
    • addedInput schema / properties / query / minLength
      Added value: +3
    • addedOutput schema / properties / hasMore
      Added value: +{
+  "description": "True when more gaps matched than the list carries (the query is limit-clamped). Offer to narrow or paginate rather than implying the list is everything.",
+  "type": "boolean"
+}
    • addedOutput schema / properties / scope
      Added value: +{
+  "description": "get_top_gaps only: 'weekly' = the source complaints are from the last 7 days; 'all-time' = the week was empty, so these are the highest-intent gaps overall.",
+  "enum": [
+    "weekly",
+    "all-time"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / total / description
      Added value: +"Exact number of gaps matching the query in the corpus, NOT the length of the list above -- the list is capped by `limit`. Quote this, not gaps.length, when telling the user how much demand there is."
    • addedOutput schema / properties / weekOf
      Added value: +{
+  "description": "get_top_gaps only, present with scope 'weekly': the UTC date the 7-day window opened (YYYY-MM-DD).",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "gaps",
-  "total",
-  "dossierUrl",
-  "attribution"
-]New value: +[
+  "gaps",
+  "total",
+  "hasMore",
+  "dossierUrl",
+  "attribution"
+]
  2. Changed1 schema field changed
    • addedOutput schema / properties / upgradeUrl
      Added value: +{
+  "description": "Present only when the caller's plan does not include full dossiers: the page that unlocks them. Surface it when the user wants depth the teaser does not have.",
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • addedOutput schema / properties / gaps / items / properties / publicUrl
      Added value: +{
+  "description": "Public page for this gap, readable with no account: the complaint, the scores, and how it compares in its category. Offer this first.",
+  "type": "string"
+}
    • changedOutput schema / properties / gaps / items / properties / url / description
      Previous value: -"Link to give the user for this specific gap."New value: +"Link to this gap's full dossier. Requires a free account; anonymous visitors are redirected to signup and land back on THIS gap."
  4. Changed2 schema fields changed
    • addedOutput schema / properties / gaps / items / properties / category / description
      Added value: +"Broad product category, e.g. 'E-commerce' or 'DevTools'. Reusable as the category filter."
    • addedOutput schema / properties / gaps / items / properties / title / description
      Added value: +"The opportunity, phrased as what is missing."
  5. Changed1 schema field changed
    • addedOutput schema / properties / gaps / items / properties / url
      Added value: +{
+  "description": "Link to give the user for this specific gap.",
+  "type": "string"
+}
  6. Changed2 schema fields changed
    • removedOutput schema / properties / gaps / items / properties / trending
      Removed value: -{
-  "type": "boolean"
-}
    • changedOutput schema / properties / gaps / items / required
      Previous value: -[
-  "id",
-  "title",
-  "category",
-  "commercialIntent",
-  "confidence",
-  "trending"
-]New value: +[
+  "id",
+  "title",
+  "category",
+  "commercialIntent",
+  "confidence"
+]
  7. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful domain context beyond that: results are real recurring complaints scored for commercial intent (willingness to pay), which tells the agent what the returned data represents.

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?

Three tight sentences with no waste: what it does, what the data is, and when to use it. Purpose and the value proposition are front-loaded.

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 structure needn't be described, and the description covers purpose, triggering conditions, and data semantics. The only gap is explicit differentiation from the sibling tools, which would help an agent choose correctly.

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%, with all three parameters documented including examples for query and bounds for limit. The description adds no parameter-level detail beyond the schema, so the baseline of 3 is 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?

States a specific verb and resource ('Search validated software opportunities by keyword') and clarifies what a 'gap' is. It distinguishes itself somewhat from get_top_gaps by implying keyword-driven search, but never explicitly contrasts with the sibling that presumably returns unfiltered top results.

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

Usage Guidelines4/5

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

Gives clear triggering conditions: 'Use this when the user wants ideas in a specific market, or asks what people complain about in some domain.' No when-not guidance and no mention of alternatives like get_top_gaps or validate_idea, so it stops short of full routing guidance.

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

All DDMarketer toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources