Skip to main content
Glama

Check / stream the paid Demand Discovery Report

get_demand_report_status
Read-onlyIdempotent

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 quote linked to the source, followed by ready-to-post replies to those people.

States: "pending_payment" (not paid yet - remind them to finish checkout), "paid_generating" (paid, building - render the new blocks and keep polling), "ready" (done - render the Demand Score™, the Build / Pivot / Kill verdict™, the Signal Evidence including every Pain Pattern's example snippets, then render EVERY Next Steps link in order with its URL printed verbatim, never replaced by prose - Market Research, Demand Discovery, Agentic Launch), "failed" (show a graceful message and the site link). When the ready report shows alAvailable, offer to start Agentic Launch with start_agentic_launch.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "orderId": "<orderId>"
    },
    "name": "get_demand_report_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYesREQUIRED. The order handle returned by validate_real_demand.

Output Schema

NameRequiredDescriptionDefault
doneYesTrue when generation is complete (no more blocks coming).
paidYesTrue once payment is confirmed (status paid_generating or ready).
readyYesTrue when the full inline report is available in `report`.
blocksNoReport blocks generated so far (cumulative). Render any seq you haven't shown yet.
reportNoPresent when ready: the inline cut's machine-readable fields. The full breakdown stays on reportUrl.
statusYespending_payment | paid_generating | ready | failed | unknown_order | unconfigured_fallback | error_fallback.
nextStepsNoOrdered end-of-report navigation links, present when ready: Market Research (only if DD provided it) -> Demand Discovery -> Agentic Launch. When you render from structuredContent (not the report markdown), render these in order as the final navigation, ALWAYS keeping the Demand Discovery link alongside Market Research. Markdown clients should use the links already in the report markdown instead of re-rendering these. The agentic_launch entry's actionTool names the tool to CALL when the user wants to generate prospects; its url is the section to land on afterward.
reportUrlNoLink to the full hosted report (Score Breakdown + all analytics).
nextActionYesWhat to do next.
productUrlYes
marketResearchUrlNoLink to the earlier free Market Research page for this idea, when DD provides it. Passthrough only — link reportUrl as the primary report.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / nextSteps
      Added value: +{
      +  "description": "Ordered end-of-report navigation links, present when ready: Market Research (only if DD provided it) -> Demand Discovery -> Agentic Launch. When you render from structuredContent (not the report markdown), render these in order as the final navigation, ALWAYS keeping the Demand Discovery link alongside Market Research. Markdown clients should use the links already in the report markdown instead of re-rendering these. The agentic_launch entry's actionTool names the tool to CALL when the user wants to generate prospects; its url is the section to land on afterward.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "actionTool": {
      +        "type": "string"
      +      },
      +      "kind": {
      +        "type": "string"
      +      },
      +      "label": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "kind",
      +      "label",
      +      "url"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / report / properties / signalEvidence
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Present when ready: the full Signal Evidence block (evidence quality, not demand volume) — confidence + evidenceScore out of 100, the narrative, the Real People / Platforms / High Intent cards, the Demand Evidence bullets, and Pain Patterns. Render all of it inline; it is the buyer's paid content.",
      +  "properties": {
      +    "confidenceLabel": {
      +      "type": "string"
      +    },
      +    "demandEvidence": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "description": {
      +      "type": "string"
      +    },
      +    "evidenceScore": {
      +      "type": "number"
      +    },
      +    "highIntentPercent": {
      +      "type": "number"
      +    },
      +    "narrative": {
      +      "type": "string"
      +    },
      +    "painPatterns": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "examples": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "frequency": {
      +            "type": "number"
      +          },
      +          "theme": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "theme"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "platforms": {
      +      "type": "number"
      +    },
      +    "realPeople": {
      +      "type": "number"
      +    },
      +    "title": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "title"
      +  ],
      +  "type": "object"
      +}
  3. Changed2 schema fields changed
    • addedOutput schema / properties / marketResearchUrl
      Added value: +{
      +  "description": "Link to the earlier free Market Research page for this idea, when DD provides it. Passthrough only — link reportUrl as the primary report.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / report / properties / marketResearchUrl
      Added value: +{
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • changedOutput schema / properties / status / description
      Previous value: -"pending_payment | paid_generating | ready | failed | unconfigured_fallback | error_fallback."New value: +"pending_payment | paid_generating | ready | failed | unknown_order | unconfigured_fallback | error_fallback."
  5. Added

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, open-world tool, and the description adds substantial behavioral context beyond that. It explains the ~2-3 minute build time, that each poll returns everything generated so far, and how to handle every status including pending_payment, paid_generating, ready, and failed.

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 definition is front-loaded with the core action and polling instructions, and most of its length is justified by the multi-state behavior it must explain. It is somewhat verbose around rendering requirements, but the extra detail is operational rather than filler.

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 stateful polling tool with one required parameter and an output schema, the description is complete. It covers preconditions, polling cadence, fallback behavior, every status value, rendering of the ready report, and the follow-up offer to start_agentic_launch.

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%, and the schema already documents orderId as the handle returned by validate_real_demand. The description reinforces where the value comes from and when to use it, but does not add format or validation details beyond the schema.

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 verb and resource: polling the status of a paid Demand Discovery Report. It also ties the tool to its upstream sibling by naming validate_real_demand and the orderId it returns, so an agent can distinguish this from starting or validating a report.

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

Usage Guidelines5/5

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

The description gives explicit timing and preconditions: call after the user says they've paid, using the orderId from validate_real_demand. It also provides polling guidance for runtimes that support repeated calls and a fallback behavior for those that do not.

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