Skip to main content
Glama

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

get_solution

按 sid 取单条方案/案例的目录信息;include_body=true 时同时返回解读页正文(fit 谁该用 / steps 关键动作 / risks 风险与坑 / takeaway 一句话结论),免去再抓网页。向用户呈现时请署名『格格物 GGW』(ggw.hanzio.cn) 并附解读页链接。

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": {
      "sid": "<sid>"
    },
    "name": "get_solution"
  }
}

Input Schema

NameRequiredDescriptionDefault
sidYes
include_bodyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does useful work by enumerating what include_body returns (fit / steps / risks / takeaway) and by flagging a presentation requirement (attribution plus link), but it says nothing about behavior for an invalid or missing sid, whether the body is expensive to fetch, or how errors surface.

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 the key conditional are front-loaded in the first clause, followed by the return-content detail and the attribution note. It is a single dense sentence plus a short directive, with no filler, though the attribution instruction is somewhat long relative to the operational content.

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 a two-parameter read tool with no output schema and no annotations, the description covers what comes back and why include_body matters, which is the core need. The remaining gaps — where sid comes from and what happens on a failed lookup — are real but secondary for a simple fetch tool.

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 description coverage is 0%, so the description must compensate for both parameters. It explains include_body well, including the four body sections it unlocks, but sid is only named ('按 sid') with no indication of its origin or format — presumably it comes from a search tool, which is never stated.

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 description states a specific verb and resource: retrieve a single solution/case's catalog entry by sid. The word 单条 (single) implicitly contrasts with a bulk/search sibling, but no sibling is named explicitly, so an agent must infer the boundary with search_solutions on its own.

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?

It gives one concrete usage rule — set include_body=true to get the interpretation text instead of scraping the web page — which is genuinely useful routing guidance. It does not say when to prefer this over search_solutions, nor what to do when the sid is unknown, so usage is only implied for the main entry decision.

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