DDMarketer

This week's highest-intent gaps

get_top_gaps

Read-only

Return the highest commercial-intent validated gaps from the past week, across all categories. Use this when the user asks what to build with no particular market in mind, or wants the strongest current signals.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max gaps to return (1-25, default 10).
`category`	No	Optional exact category filter.

Output Schema

TableJSON Schema

Name	Required	Description
`gaps`	Yes
`loose`	No	True when no gap matched all your terms and these are loosely related instead. Not validation.
`total`	Yes
`dossierUrl`	Yes
`upgradeUrl`	No	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.
`attribution`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 4, 2026

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"
+}

Changed2 schema fields changedSep 2, 2026

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."

Changed2 schema fields changedAug 29, 2026
- 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."
```

Changed1 schema field changedAug 28, 2026

addedOutput schema / properties / gaps / items / properties / url

Added value: +{
+  "description": "Link to give the user for this specific gap.",
+  "type": "string"
+}

Changed2 schema fields changedAug 28, 2026

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"
+]

First observedAug 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds meaningful selection behavior: results are filtered to 'validated' gaps, ranked by 'commercial-intent', and limited to 'the past week'. This discloses the tool's core filtering logic, which annotations cannot convey.

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?

Two sentences, zero filler. The core action and scope are front-loaded in the first sentence, with usage guidance in the second. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a simple two-parameter tool with an output schema, read-only annotations, and optional parameters only. Purpose, scope, usage cue, and selection behavior are all covered; nothing an agent needs to call it correctly is missing.

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% — both 'limit' and 'category' are already documented in the input schema. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline score of 3 applies.

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?

States a specific verb ('Return'), a precise resource ('validated gaps'), and clear scope ('highest commercial-intent', 'past week', 'across all categories'). The phrase 'across all categories' implicitly distinguishes it from category-scoped siblings, making the tool's identity unmistakable.

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 an explicit when-to-use condition: 'when the user asks what to build with no particular market in mind, or wants the strongest current signals.' This is clear and actionable, though it stops short of naming alternatives or stating explicit when-not-to-use scenarios.

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

All DDMarketer tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clearly distinct role: browse top gaps, search gaps by keyword, retrieve a full dossier for a specific gap, and validate a new idea. The descriptions make the boundaries between list, search, detail, and evaluation obvious, so an agent should rarely misselect.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: get_dossier, get_top_gaps, search_gaps, validate_idea. The verb clearly signals the action and the noun identifies the resource, making the naming predictable.

Tool Count5/5

With four tools, the server is tightly scoped for market-gap discovery and validation. Each tool covers an essential part of the workflow without redundancy, and the count is comfortably within the ideal range.

Completeness5/5

The tool surface covers the main user journeys: finding trending opportunities, searching by market, drilling into one gap, and testing a custom idea. There are no obvious dead ends or missing operations for the server's stated purpose.

This week's highest-intent gaps

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources