Skip to main content
Glama

set_group_new_member_history_visibility

Set whether new members can view historical messages in a QQ group; success depends on the current account's permissions in that group.

Instructions

设置新成员是否可查看历史消息 替换群号和成员 QQ 号;操作是否允许取决于当前账号在该群的权限。

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>",
      "visible": "<visible>"
    },
    "name": "set_group_new_member_history_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
visibleYes
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already state readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is largely covered. The description adds a real behavioural fact beyond that — the call is permission-gated by the account's role in the group — but it says nothing about failure modes, side effects on existing members, or response shape.

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?

The text is short and front-loads the actual purpose, which is good. However, the middle clause about substituting group and member QQ numbers reads like leftover boilerplate and muddies the otherwise clean statement.

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 write toggle with annotations and no output schema, the definition covers the core purpose and the permission caveat. It falls short by not clarifying the true/false semantics explicitly and by naming a parameter that isn't part of the schema, which an agent could stumble on.

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 50%: group_id is documented, visible is not, so the description must compensate. It does clarify that the boolean governs whether new members see history, but it also references a 'member QQ number' parameter that does not exist in the schema — actively misleading about what to supply.

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: toggling whether newly joined members can view historical messages in a group. That is concrete enough for an agent to distinguish it from siblings like set_group_whole_ban or set_group_add_option. It just doesn't explicitly contrast itself against any neighbour.

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?

There is no explicit when-to-use or when-not guidance and no named alternative. The one useful cue is that the operation is permitted only if the current account has sufficient privileges in that group, which implies a precondition but leaves the agent to infer the rest.

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