Skip to main content
Glama

格格物 GGW · 中小企业 AI 落地(B2A)

run_pain_quiz

代用户运行「七道关」痛点自测,返回结构化诊断(gates 排序/top_gate/top_biz/scene/推荐方案)与回看链接。⚠️ 必须先调 get_pain_quiz:把 10 道题逐题问用户(列出全部选项原文,单选选一个、多选可多选),把选中选项的 B*/T* 权重累加成 biz/pain,并把选中项给出的 maturity/readiness、industry/role 一起传入;只传画像不传 biz/pain 会返回 scored:false。

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

Input Schema

NameRequiredDescriptionDefault
bizNo
painNo
roleNo
testNo
sceneNo
industryNo
maturityNo
readinessNo

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?

With no annotations, the description carries the full behavioral burden, and it does disclose the response shape, the review-link artifact, and a specific failure mode (scored:false) rather than leaving the agent to discover it by trial. It stays silent on whether the run persists a record, whether re-running overwrites a prior diagnosis, and what permissions are needed – gaps that matter for a tool whose name implies an execution step.

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?

Purpose and return payload are front-loaded, followed by a clearly flagged ⚠️ precondition block, which is the right ordering for a tool with a mandatory prerequisite. The middle sentence packs a lot – question delivery, single vs multi-select, weight aggregation – into one run-on clause, but given 0% schema coverage that detail earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, mutation-implied tool with no annotations and no output schema, the description covers the workflow, the failure mode, and the result fields well. It is still incomplete on the 'test' parameter, the 'scene' input, and any statement about side effects or storage, which an agent would need before invoking it confidently.

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 0% across 8 parameters, so the description must compensate, and it does explain how biz/pain are constructed (accumulated B*/T* weights from selected options) and that maturity/readiness/industry/role come from the selected items. However the boolean 'test' parameter is never mentioned, and 'scene' appears only as an output field, leaving its input semantics and the interaction between the two undocumented.

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?

States a specific verb and resource ('run the Seven Gates pain self-assessment on behalf of the user') and enumerates the actual return payload (gates ranking, top_gate, top_biz, scene, recommended solutions, review link). It also distinguishes itself from the sibling get_pain_quiz by making that tool an explicit prerequisite, so an agent can tell the two apart without opening either schema.

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?

Gives a hard ordering rule (must call get_pain_quiz first, ask all 10 questions, aggregate B*/T* weights) plus a when-not condition: passing only profile data without biz/pain yields scored:false. What it lacks is routing relative to the other diagnostic-flavored siblings such as request_diagnosis or get_solution, so an agent still has to infer which diagnostic path applies.

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