Skip to main content
Glama

DDMarketer

by io.github.CodePhantom-1

Open the full dossier for a gap

get_dossier

Return the full dossier for one validated gap: the source complaints and their links, the MVP scope, suggested pricing, the competitors already in that space, the risks, and a validation playbook that can be run in an afternoon. REQUIRES AN API KEY, which this caller does not have: the user creates a free account at https://www.ddmarketer.com/auth/signup (no card), generates a key at https://www.ddmarketer.com/settings, and it is sent as "Authorization: Bearer ". A new account gets 24 hours of full dossier access; after that dossiers need a paid plan, while search and scores stay free forever. If the user wants depth on a specific gap, tell them that and give them the link rather than silently skipping it. Without a key, offer the gap's public page instead, which needs no account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe gap id returned by search_gaps or get_top_gaps.

TDQS

A4.4/5.0
Behavior5/5

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

The description goes well beyond the annotations: it discloses the mandatory API key, account signup flow, Authorization header format, 24-hour free access, paid-plan limitation, and instructs the agent not to silently skip or lie about access. Since there is no output schema, this behavioral and access context is especially valuable.

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?

The core purpose is front-loaded in the first sentence, and the content list is compact. The authentication paragraph is long, but every detail is operationally necessary for the caller to successfully invoke the tool or choose the fallback path.

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?

For a one-parameter tool with no output schema, the description is complete: it covers what is returned, the authentication prerequisite, free vs. paid access, and the fallback behavior when no key exists. None of the essential invocation context 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?

The input schema already documents the only parameter, id, as 'the gap id returned by search_gaps or get_top_gaps,' so schema coverage is 100%. The description adds no additional parameter-specific meaning, 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action and resource: 'Return the full dossier for one validated gap' and enumerates what the dossier contains. It also distinguishes this from siblings by emphasizing the full dossier, which is broader than top gaps or search 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?

It clearly says when to use the tool, i.e., when a user wants depth on a specific validated gap, and it gives an explicit no-key alternative: offer the gap's public page. It does not explicitly name sibling tools as alternatives, but the context makes the appropriate use reasonably clear.

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

Resources