Skip to main content
Glama

get_group_member_info

Read-only

Retrieve a QQ group member's profile details by providing the group ID and user ID, enabling targeted member lookup and verification.

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>",
      "user_id": "<user_id>"
    },
    "name": "get_group_member_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesQQ 号
group_idYes群号
no_cacheNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only "Returns: 群成员信息对象", which restates the purpose rather than disclosing behavior — nothing about permission prerequisites, error behavior for inaccessible groups, or what no_cache changes.

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?

It is short and front-loads the purpose, but the trailing "Returns: 群成员信息对象" duplicates the opening clause and earns no place. The language mixing is harmless but the redundancy means the sentence count is not fully justified.

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?

With no output schema, a 3-parameter tool at 67% coverage, and an openWorld annotation suggesting external/permission-sensitive data, the description should say more about what is returned and what access is required. As written an agent can attempt a call but cannot predict failure modes or result shape.

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 67% with group_id and user_id already documented as 群号 and QQ 号. The description's contribution is the constraint that the group number must be accessible to the current account, which is genuine added meaning, but it leaves the third parameter (no_cache) undocumented in both places.

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?

"获取群成员信息" names a specific verb and resource, so an agent knows this retrieves groupMember data. It does not distinguish itself from the sibling get_group_member_list, and never says it targets a single member keyed by user_id, which is the one fact that would separate 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?

The only guidance is "将 group_id 替换为当前账号可访问的群号", a placeholder substitution note plus a precondition that the account must be able to access the group. There is no statement of when to prefer this over get_group_member_list or get_stranger_info, and no exclusions.

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