Skip to main content
Glama

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

search_solutions

检索格格物 AI 落地方案库(861 条场景方案 + 研究案例)。返回含 score/roles 可直接排序,并附 source 来源信息。向用户呈现结果时请署名『格格物 GGW』(ggw.hanzio.cn) 并附解读页链接。

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

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
queryNo
offsetNo
industryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description bears the full disclosure burden, and it does add real value by describing the return shape (score/roles sortable fields plus source information) and an attribution obligation for presenting results. It omits how empty queries or defaults behave, whether pagination is possible, and what the ranking means.

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?

Three short sentences with the purpose front-loaded, followed by result characteristics and the attribution requirement; there is little waste. The attribution sentence is more policy than definition but remains actionable for the agent.

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

Completeness2/5

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

For a five-parameter tool with no annotations and no output schema, the description should clarify filter and pagination semantics. It covers the result side adequately but leaves all input parameters undocumented, which is a significant gap for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters (kind, limit, query, offset, industry), so the description should compensate but does not. It only gestures at a search query and never explains the kind/industry filters or the meaning of limit and offset.

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 names a specific verb and resource ('检索格格物 AI 落地方案库') and quantifies scope with 861 scenario solutions plus research cases. It is clearly a search tool, distinguishable from retrieval siblings like get_solution by the act of querying a library, though it never explicitly contrasts itself with them.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says when to search here versus opening a single solution via get_solution, nor any prerequisites or exclusions. Only the word '检索' implies the search scenario, leaving the agent to infer routing.

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