product-spec-mcp

需求追问

spec_interrogate

Analyze raw product ideas to determine development readiness. Generate follow-up questions when input lacks necessary details.

Instructions

分析用户的原始 idea 或页面修改需求，判断信息是否足够进入开发阶段。当信息缺失较多时，输出追问问题清单。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`raw_idea`	Yes	用户原始表达，必填
`scenario`	No	场景类型	unknown
`target_platform`	No	目标平台	unknown
`strictness`	No	追问严格程度	normal
`known_context`	No	已知上下文信息

Output Schema

TableJSON Schema

Name	Required	Description	Default
`readiness`	Yes
`clarification`	Yes
`recommendation`	Yes
`technicalProfile`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.20Jun 23, 2026

addedOutput schema / properties / clarification / properties / questions / items / properties / example
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / technicalProfile

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "blockers": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "confidence": {
+      "enum": [
+        "high",
+        "medium",
+        "low"
+      ],
+      "type": "string"
+    },
+    "evidence": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "frontendOnly": {
+      "type": "boolean"
+    },
+    "needsAdmin": {
+      "type": "boolean"
+    },
+    "needsAuth": {
+      "type": "boolean"
+    },
+    "needsBackend": {
+      "type": "boolean"
+    },
+    "nextQuestions": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "example": {
+            "type": "string"
+          },
+          "question": {
+            "type": "string"
+          },
+          "why": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "question",
+          "example",
+          "why"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "shape": {
+      "enum": [
+        "static_page",
+        "local_storage_tool",
+        "local_json_import_export",
+        "static_json_data_page",
+        "light_backend_json_sqlite",
+        "full_backend_saas",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "suggestedStorage": {
+      "enum": [
+        "none",
+        "localStorage",
+        "indexedDB",
+        "static_json",
+        "json_file",
+        "sqlite",
+        "postgresql"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "shape",
+    "confidence",
+    "frontendOnly",
+    "needsBackend",
+    "needsAuth",
+    "needsAdmin",
+    "suggestedStorage",
+    "evidence",
+    "blockers",
+    "nextQuestions"
+  ],
+  "type": "object"
+}

First observedv1.0.0Jun 21, 2026

TDQS

A4/5.0

Behavior3/5

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

The description explains the core behavior (analyze, judge sufficiency, output questions) but doesn't specify the output format when info is sufficient, whether it modifies any state, or any authentication or rate limit requirements. With no annotations, the description carries the full burden, and more details would improve transparency.

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

Conciseness5/5

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

The description is two sentences, directly stating the purpose and output. It is front-loaded and every sentence earns its place with no waste.

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?

Given the presence of an output schema and 5 params (with 3 enums), the description covers the main behavior. However, it could mention the output structure more explicitly (though output schema exists) and discuss error handling or edge cases for missing info.

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 coverage is 100%, so baseline is 3. The description adds little beyond the schema; it mentions the raw_idea is required but doesn't elaborate on parameter meanings or usage nuances. The schema already provides sufficient descriptions for each parameter.

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 clearly states it analyzes raw ideas or page modifications to determine if info is sufficient for development, and outputs follow-up questions if needed. This distinguishes it from siblings like spec_compile (which likely compiles to a spec) or product_spec_assist (which assists in writing specs).

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 implies usage when user input is vague and needs clarification before development, and notes when info is missing. However, it doesn't explicitly differentiate from siblings or state when not to use this tool versus alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server