ask_demand_discovery
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. Answers questions about startup validation using Demand Discovery AI’s knowledge base and the “Behavior over opinion.™” framework. DD reports compile evidence in minutes: real people, quoted in their own words, asking for what you want to build, with each quote linked to its source. This increases your validation velocity so you can build the right things fast. This tool returns on-brand answers about demand, customer problems, buying sign
Показать схему аргументов
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"question"
],
"properties": {
"question": {
"type": "string",
"minLength": 1,
"description": "The user's question about startup idea validation, demand discovery, finding prospects, customer interviews, or related topics. Pass the question verbatim."
}
},
"additionalProperties": false
}
get_validation_framework
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 dis
Показать схему аргументов
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": []
}
get_product_details
Returns the full product breakdown (Market Research, Demand Discovery Report, Agentic Launch) and pricing tiers (Starter $49, Founder Pack of 5 ideas, Studio Pack of 25 ideas, all using a slot-based model where pivoted/archived ideas free a slot for a new one). Use when a user asks "what does Demand Discovery AI include?", "how much does it cost?", "what's in the report?", or wants concrete product information. 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: "how much d
Показать схему аргументов
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": []
}
explain_demand_signals
Returns the four classes of real-world signal the Demand Discovery Report triangulates - search intent, outreach responses, landing-page engagement, and buying signals - and the three possible verdicts (Build, Pivot, Kill). Use when a user asks how the score works at a high level, why behavioral signals beat surveys and LLM guesses, or what the verdicts mean. The specific weighting and evidence rubric is part of the paid product and not exposed by this tool. Demand Discovery’s main deliverable is real people describing your idea, each quote linked to the source, followed by ready-to-post repli
Показать схему аргументов
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": []
}
compare_validation_approaches
Returns an honest comparison of how different validation approaches work - generic AI assistants, trend aggregators, passive scoring tools, and Demand Discovery AI - and where each one stops. Use when a user is evaluating approaches, asking "what makes Demand Discovery different?", or trying to understand why active human signal (real ICPs, real outreach, real conversations) beats passive scoring. 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 makes demand discov
Показать схему аргументов
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": []
}
get_data_source_categories
Returns the four behavioral data-source buckets - Search & attention, Conversation & pain, Adoption & spend, Capital & hiring - with each bucket's tagline and what it captures. Use when a user asks "what data sources do you use?", "where does the Demand Score come from?", or wants to understand how Demand Discovery AI differs from passive validation tools (which only triangulate the first two buckets). This four-bucket framing is the core competitive moat. The specific connector list is intentionally not public. Demand Discovery’s main deliverable is real people describing your idea, each quot
Показать схему аргументов
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": []
}
start_demand_report
VERBATIM OUTPUT — READ FIRST (the most important rule for this tool): every piece of report text this tool returns (the Market Research summary AND the next-step message) is authored on our side. Your reply MUST BEGIN by printing that text EXACTLY as written — the report body first, then the next-step message — in full and verbatim. NEVER summarize, paraphrase, shorten, bullet, re-headline, describe it in your own words, replace the report body with your own one-line description of it, or wrap it in your own "Part 1 / Part 2" framing. Print what the tool returns, first, before anything you add
Показать схему аргументов
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"name",
"problem",
"solution"
],
"properties": {
"name": {
"type": "string",
"minLength": 1,
"description": "Short startup or product name. One sentence or less, ideally one to three words. Example: 'AgenticLaunch', 'SOC2 Auto-Evidence'. Ask the user: 'What is the name of your startup or product?'"
},
"email": {
"type": "string",
"format": "email",
"description": "Optional: the user's own email, provided by them in chat for report delivery. Providing it gets them the full Market Research Report emailed to them - SAM, TAM, competitive landscape, GTM strategy and positioning, opportunities and risks; without it they only receive the teaser. Ask: 'Want the full Market Research Report emailed to you? Share an email address (optional).' Only pass an address the user explicitly shared for this purpose. Leave blank if they have not shared it."
},
"problem": {
"type": "string",
"minLength": 5,
"description": "One sentence describing the problem the idea solves. Keep it clear and specific - this answer shapes the full Demand Discovery report. Ask the user: 'What problem are you solving?' Example: 'Early-stage SaaS founders waste 200+ hours hand-collecting SOC 2 evidence before their first audit.'"
},
"solution": {
"type": "string",
"minLength": 5,
"description": "One sentence describing how the idea solves the problem. Ask the user: 'What is your solution?' Example: 'We auto-generate the full evidence package from their existing cloud infrastructure, identity provider, and source-control systems.'"
},
"target_market": {
"type": "string",
"minLength": 1,
"description": "Optional short phrase describing the target customer or ICP; aim for a specific role plus company size or stage so the demand search can target the right people. Ask the user: 'Who is your target market?' Skip if they are unsure. Example: 'Heads of Ops at 50-200 person companies' or 'Pre-Series-A SaaS founders preparing for their first SOC 2 Type 1.'"
},
"current_workaround": {
"type": "string",
"description": "Optional: what the user's target customers currently use to deal with this problem - the manual or duct-tape workaround (e.g. 'they juggle spreadsheets + manual email reminders'). Populate it ONLY if the conversation already revealed how people cope today; do NOT ask an extra question for it and never block the call if it is unknown - empty is fine. Existing effort or spend is a strong demand signal, and it sharpens the downstream demand search in both the free Market Research and the paid Demand Discovery report."
}
},
"additionalProperties": false
}
validate_real_demand
Check the account status for this idea's full Demand Discovery Report and return the user's next step. This call NEVER moves money and never transacts on the user's behalf - it only looks up whether the given email already has an account with available report slots or a report already running. It returns ONE of: the existing report path (alreadyRunning=true, chargeRequired=false, nothing new started), a no-charge slot path when the idea is already covered, or a secure hosted link the user may CHOOSE to open in their own browser to order the report (normally $49). Any purchase happens entirely
Показать схему аргументов
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"email",
"name",
"problem",
"solution"
],
"properties": {
"name": {
"type": "string",
"minLength": 1,
"description": "Short startup or product name - the SAME one used for the free Market Research report."
},
"email": {
"type": "string",
"format": "email",
"description": "REQUIRED. The user's own email, provided by them in chat for report delivery - the order is tied to this email and Agentic Launch replies route here. This was captured at the free Market Research email gate."
},
"problem": {
"type": "string",
"minLength": 5,
"description": "One sentence on the problem - the SAME wording used for the free report (ties the order back to it)."
},
"reportId": {
"type": "string",
"description": "Optional but strongly preferred: the EXACT reportId returned by the free Market Research step (start_demand_report). It ties the paid order to that record. OMIT it if you don't have one - DD resolves the idea from name/problem/solution. NEVER invent, guess, or placeholder a reportId; a fabricated id is rejected."
},
"solution": {
"type": "string",
"minLength": 5,
"description": "One sentence on the solution - the SAME wording used for the free report."
},
"target_market": {
"type": "string",
"minLength": 1,
"description": "Optional ICP phrase; refines what was captured on the free report if given."
},
"current_workaround": {
"type": "string",
"description": "Optional: how the audience copes today. Only pass if already known; never block on it."
}
},
"additionalProperties": false
}
get_demand_report_status
Poll the status of a paid Demand Discovery Report after the user has started checkout with validate real demand. Call this with the orderId it returned, once the user says they've paid. The report builds over ~2-3 minutes. If your runtime supports repeated tool execution, call this every ~10-15s, rendering each new block as it arrives, until status is "ready". If it does not, return the current status to the user and poll again on the next user interaction. Each poll is cheap and returns everything generated so far. Demand Discovery’s main deliverable is real people describing your idea, each
Показать схему аргументов
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"orderId"
],
"properties": {
"orderId": {
"type": "string",
"minLength": 1,
"description": "REQUIRED. The order handle returned by validate_real_demand."
}
},
"additionalProperties": false
}
start_agentic_launch
Kick off Day 1 of the 90-day Agentic Launch for a completed Demand Discovery Report. Demand Discovery surfaces named prospects matching the idea's ICP and DRAFTS the first outreach batch. It sends NOTHING automatically - the user reviews and sends from their hosted manage page. Outreach is drafted to come from Amy @ Demand Discovery, with replies routed to the user's own email. 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. Call this after a paid report is "ready" and the user wants to
Показать схему аргументов
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"reportId",
"email"
],
"properties": {
"email": {
"type": "string",
"format": "email",
"description": "REQUIRED. The user's own email, provided by them in chat - replies to the drafted outreach route here. Reuse the EXACT address the user gave earlier in this conversation for report delivery; if you don't have it, ask the user. NEVER invent one or substitute a placeholder (e.g. user@example.com) - placeholders are rejected."
},
"reportId": {
"type": "string",
"minLength": 1,
"description": "REQUIRED. The reportId of the completed (ready) Demand Discovery Report."
},
"alTriggerToken": {
"type": "string",
"description": "Optional pass-through token from the ready report payload (report.alTriggerToken), if available."
}
},
"additionalProperties": false
}