Skip to main content
Glama

get_group_admin_settings

Read-only

Fetch current group admin settings for a QQ group ID to review permissions and management configuration before updating them.

Instructions

获取群管理设置的当前值 将 group_id 替换为当前账号可访问的群号。 Returns: 与对应设置接口字段对齐的当前群管理设置。

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_admin_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the access-scoping constraint on the group and the fact that returned fields align with the corresponding settings interface, which helps pair it with a setter, but says nothing about required admin privileges or error behavior when the account lacks access.

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 short sentences plus a labeled Returns clause; the resource is front-loaded and there is no filler to trim.

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 one-parameter read tool this is adequate, but with no output schema the description should say what the returned settings contain — 'aligned with corresponding settings interface fields' is too vague to let an agent know what keys to expect or whether nulls/empties are possible.

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 coverage is 100% with a single required group_id already documented as 群号, so the schema carries the parameter burden. The description adds only the access constraint (必须为当前账号可访问的群), which is mildly useful but close to restating the field.

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?

States a specific verb and resource: fetching the current values of group admin settings (获取群管理设置的当前值). It is a clear read operation, though it does not explicitly distinguish itself from the similarly named sibling get_group_admin_permissions, leaving the scope of 'admin settings' versus 'permissions' to inference.

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 only implied — an agent is expected to call this before or after a corresponding set operation, but no when-to-use or when-not-to-use guidance is given, and no sibling is named as an alternative. The one concrete guideline is a prerequisite: group_id must be a group number accessible to the current account.

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