Skip to main content
Glama

Get the Demand Score and signals explained

explain_demand_signals
Read-onlyIdempotent

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 replies to those people.

Trigger phrases: "demand score", "what is the demand score", "0 to 100 score", "behavioral signals", "buying signals", "build pivot kill", "build/pivot/kill", "build pivot or kill", "verdict", "why behavioral signals", "why not surveys", "what counts as real demand", "what are buying signals", "is prior spend a signal", "are complaints a demand signal", "what proves people want this", "how do I spot real demand", "what's a workaround signal".

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": "explain_demand_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
verdictsYesThe three possible Demand Discovery Report verdicts and their criteria.
guaranteeYes
productUrlYes
scoreRangeYesThe 0-100 score range used for the Demand Score.
signalClassesYesThe four classes of real-world signal triangulated into the score.
whyBeatsOpinionYesWhy behavioral signals beat surveys and LLM guesses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is read-only, non-destructive, idempotent, and closed-world. The description adds useful behavioral context: it returns conceptual explanation content and does not expose the paid weighting or evidence rubric. It does not specify whether the content is static or dynamically assembled, but the output schema covers the return shape.

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 purpose and usage guidance are front-loaded, which is good. However, the middle paragraph about Demand Discovery's main deliverable reads as marketing context rather than invocation guidance, and the trigger-phrase list is very long, making the definition longer than necessary.

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 zero-parameter, read-only explanatory tool with annotations and an output schema, the description covers what it returns, when to use it, and an important limitation about withheld weighting details. Nothing essential for correct invocation is missing.

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 has zero parameters, so parameter semantics are inherently minimal. The description correctly adds no unnecessary parameter detail, and the baseline of 4 is appropriate.

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 first sentence states specifically that the tool returns the four signal classes and three verdicts, and the usage sentence says to use it when a user asks how the score works at a high level. The purpose is clear, but the description does not explicitly distinguish this tool from siblings such as get_validation_framework or compare_validation_approaches.

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?

The description gives an explicit 'Use when...' condition covering high-level score questions, why behavioral signals beat surveys or LLM guesses, and what verdicts mean, plus extensive trigger phrases. It also notes that specific weighting is not exposed, but it does not name an alternative tool for deeper validation 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