Skip to main content
Glama

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

get_pain_quiz

获取「七道关」自测题库(10 题:行业/角色/成熟度/数据就绪度 + 6 道多选痛点,选项带 B/T 权重)。返回体含 flow(5 步流程)/ asking(怎么问)/ example(完整示例与累加后的参数)。用法:逐题把题干与全部选项原文发给用户,单选逐题选一个、多选可多选;按选项权重累加 B*→biz、T*→pain,再调 run_pain_quiz。不要向用户展示权重。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the return body structure (flow / asking / example) and a key interaction rule about hiding weights. It omits details like whether the quiz can be re-fetched or any state/permission considerations, but for a zero-param read tool the disclosure is solid.

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?

Content is dense but front-loaded: what is returned first, then how to use it. Every sentence carries operational meaning, though the return-structure parenthetical is somewhat packed and could be split for readability.

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?

With no output schema, the description compensates by enumerating the return body fields and explaining the weight-accumulation handoff to run_pain_quiz. Nothing an agent needs to call this tool and use its result correctly appears to be 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 takes no parameters, so there is nothing for the description to clarify; the baseline of 4 applies. No parameter information is missing because none exists.

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+resource (retrieve the 'Seven Gates' self-assessment question bank) and details its contents: 10 questions covering industry/role/maturity/data readiness plus 6 multi-select pain points with B/T-weighted options. It also positions the tool relative to run_pain_quiz as the follow-up step, so an agent can tell it apart from its sibling.

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?

It gives an explicit procedural protocol: present each question and all options verbatim, pick one for single-select and multiple for multi-select, accumulate B*→biz and T*→pain by option weight, then call run_pain_quiz. It also states a clear negative constraint — do not show weights to the user.

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