Skip to main content
Glama

get_group_shut_list

Read-only

Retrieve the current mute list for a QQ group and return each still-muted member's QQ number, nickname, and mute expiry timestamp.

Instructions

获取群禁言列表 将 group_id 替换为当前账号可访问的群号。 Returns: 仍在禁言中的成员数组,每项含 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>"
    },
    "name": "get_group_shut_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, open-world behavior. The description adds that only currently muted members are returned and specifies the returned fields and timestamp unit, which is useful behavioral context beyond the annotations. It does not cover pagination, ordering, or permission requirements, so it is not a 5.

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

Conciseness5/5

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

Two sentences, with purpose front-loaded and return details appended efficiently. No filler; the returned-fields note earns its place because no output schema exists.

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

Completeness4/5

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

For a single-parameter read-only list tool with no output schema, the definition supplies the missing return shape: member array, QQ number, nickname, and expiration timestamp. Pagination and permission edge cases are not addressed, but the core call contract is complete.

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

Parameters4/5

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

Schema coverage is 100% and group_id is already described as a group number. The description adds a meaningful access constraint: the group must be accessible to the current account, going slightly beyond the schema. Baseline is 3; this small addition supports 4.

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

Purpose5/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, '获取群禁言列表', and narrows the result to members still muted, distinguishing it from a general group member list in the sibling set. An agent can identify the operation without opening the schema.

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 by the tool name and the note to supply a group number accessible to the current account, but there is no explicit when-to-use guidance, no alternatives, and no exclusion conditions. Adequate but with clear gaps.

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