Skip to main content
Glama

set_group_search

Configure how a QQ group is discoverable by setting its search mode: enable or disable group-number lookup and group-fingerprint search for a specified group.

Instructions

设置群被搜索方式(群指纹 / 群号搜索开关) 替换群号;数值含义以当前群设置为准。

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": {
      "group_id": "<group_id>"
    },
    "name": "set_group_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes群号
no_finger_openNo
no_code_finger_openNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the basic mutation/safety profile is covered. The description adds nothing beyond that: it doesn't state required permissions, whether the change is immediate, whether omitting a switch leaves it untouched (despite additionalProperties=true), or what happens on failure. For a settings-mutating call the remaining behavioral gaps are significant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short (two clauses), so nothing is wasted verbatim, but the brevity comes at the cost of clarity: the sentence is cryptic and the ordering puts the least informative clause ('替换群号') in the middle. It is compact without being front-loaded with actionable information.

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?

There is no output schema, but the tool has a simple 3-parameter shape under additionalProperties=true. Given the low schema coverage and the mutating nature of the call, the description should define the switch semantics and permissions; it instead defers value meaning to runtime, leaving the agent under-informed for the two optional parameters.

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 coverage is only 33% – group_id is documented, but no_finger_open and no_code_finger_open have no schema descriptions. The description gestures at them ('群指纹 / 群号搜索开关') but never maps each parameter to a switch or explains what integer values mean; '数值含义以当前群设置为准' explicitly defers the meaning rather than defining it, leaving the double-negative semantics ('no_finger_open') unresolved.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb and resource ('设置群被搜索方式' – set how the group can be searched) and names the two concepts being toggled (群指纹 / 群号搜索开关), which is more than a restatement of the name. However, the trailing clause '替换群号' is ambiguous and the overall phrasing is vague about exactly which settings change and in which direction.

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 statement of when to use this tool, no mention of prerequisites (e.g., bot must be group owner/admin), and no differentiation from the many sibling set_group_* tools. The agent must infer usage entirely from the name and the parameter names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools