Skip to main content
Glama

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

request_diagnosis

提交免费需求诊断留资(匿名可用,与官网表单同一护栏)。先聊 10 分钟,做不了也照实说。

    复用站点 /api/lead,标记来源为 MCP Agent(surface=mcp-agent, extra.channel=agent)。
    护栏沿用站点:蜜罐静默丢弃 + 字段白名单截断 + 每 IP 每日限流(3 次/日/IP)。

    Args:
        name: 姓名(必填,≤20 字符)。
        phone: 联系电话(必填,至少 5 位数字)。
        note: 需求备注(≤500 字符)。
        kind: lead=需求诊断 / partner=内容伙伴申请。
        client_request_id: 幂等键(≤64,仅字母数字 _ . : -)。网络超时重试请带同一键,不会重复落库/占配额。
        test: true=沙箱写入(不落真实留资表,返回 sandbox:true),用于联调。

    Returns:
        {ok, id, sandbox?, idempotent?};失败返回 {error, detail}。
    

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": {
      "name": "<name>",
      "phone": "<phone>"
    },
    "name": "request_diagnosis"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNolead
nameYes
noteNo
testNo
phoneYes
client_request_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations at all, the description carries the full burden and does so well: it discloses the per-IP daily rate limit (3/day/IP), honeypot silent-drop and field-whitelist truncation behavior, the exact idempotency contract for retries (same client_request_id does not double-write or consume quota), the sandbox mode that avoids writing to the real lead table, and the return shape on success and failure.

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?

Well front-loaded: purpose and expectations first, then transport/guardrails, then Args and Returns in scannable sections. Minor waste in restating the site guardrail twice (once in the header line, once in the guardrail paragraph) and a bit of marketing tone in the opening, but nothing that obscures the operative facts.

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 six-parameter write tool with no annotations and no output schema, the description supplies everything needed: safety constraints, rate limits, idempotency, a sandbox escape hatch, and an explicit return contract including the error form. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: all six parameters are documented with constraints the schema lacks — name ≤20 chars and required, phone ≥5 digits, note ≤500 chars, kind enum meanings (lead/partner), client_request_id ≤64 chars with an allowed charset and retry semantics, and test=true meaning sandbox with sandbox:true in the response.

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?

States a specific verb+resource in both the first line and Args: submit a free diagnosis lead (提交免费需求诊断留资), with a clear secondary mode (kind=partner for content partner applications). It is obviously distinct from the read-only quiz/solution siblings, though it never names or contrasts them explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the description tells the agent what the lead is for (a 10-minute consultation) and that it is anonymous-capable, but never says when to choose this over the sibling tools or when not to submit (e.g. disqualifying cases). The agent must infer the triggering condition from the purpose text.

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