Skip to main content
Glama

Get the Demand Discovery Framework

get_validation_framework
Read-onlyIdempotent

Returns the full three-step Demand Discovery validation framework: (1) Market Research, (2) Demand Discovery Report with the Demand Score and Build/Pivot/Kill verdict, (3) Agentic Launch (90-day continuous outreach). Use when a user asks "how do I validate an idea?", "what's the methodology?", or wants to understand the structured approach. Built on the "behavior over opinion" principle.

Demand Discovery’s main deliverable is real people describing your idea, each quote linked to the source, followed by ready-to-post replies to those people.

Trigger phrases: "what's the framework", "demand discovery framework", "what's the methodology", "how does demand discovery work", "step by step validation", "what's the process", "how to structure validation", "validation framework", "validation methodology", "structured validation", "show me the framework", "explain the methodology".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_validation_framework"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
stepsYesThe three sequential framework steps.
summaryYesOne-line summary of the framework.
philosophyYesThe core philosophy: behavior over opinion.
productUrlYes
killerPhrasesYesOn-brand phrases that capture the framework's positioning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description goes further by disclosing the payload's structure (Demand Score, Build/Pivot/Kill verdict, 90-day outreach) and the underlying 'behavior over opinion' principle, which tells the agent what kind of content to expect without needing to open the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The substantive content is front-loaded in the first two sentences, which is good. The twelve-item trigger-phrase list that closes the description is largely redundant with the example questions already given, and it inflates the definition without adding new discriminative information.

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?

This is a simple no-argument getter with an output schema, so the description does not need to explain return values. It supplies the conceptual content, invocation cues, and core principle, leaving nothing an agent needs in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misrepresents or over-promises about inputs.

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 uses a specific verb and resource ('Returns the full three-step Demand Discovery validation framework') and enumerates the three steps, so an agent knows exactly what comes back. It never names a sibling such as compare_validation_approaches or ask_demand_discovery, so the differentiation work is left undone.

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?

Usage is stated concretely: use when a user asks 'how do I validate an idea?', 'what's the methodology?', or wants the structured approach, reinforced by an extensive trigger-phrase list. There is no when-not guidance and no routing to alternatives such as compare_validation_approaches for comparative questions.

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