Skip to main content
Glama

get_group_signed_list

Read-only

Retrieve the list of members who checked in to a specified QQ group today using its group ID.

Instructions

获取群今日打卡列表 将 group_id 替换为当前账号可访问的群号。

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

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?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the access-scope constraint and identifies the data as today's check-ins, but says nothing about result size, pagination, or timezone/day boundary — details that matter for a 'today' scoped query.

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

Conciseness4/5

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

Two short clauses, resource stated first, constraint second — nothing padded. Minor redundancy in restating group_id, which the schema already declares as required.

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 with annotations and no output schema, the core identity is conveyed. What an agent still lacks is any sense of return shape (who appears in the check-in list, ordering, whether an empty list is possible) and whether the 'today' window is server-side or configurable.

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 the single parameter is documented as 群号, so the baseline is 3. The description goes beyond that by stating the value must be a group number reachable by the current account, a validity constraint the schema does not express.

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+resource: 获取 (get) 群今日打卡列表 (the group's today check-in list). The 打卡 qualifier separates it from siblings like get_group_member_list or get_group_notice, though it never explicitly names or contrasts with any alternative.

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?

Implied usage is clear from the resource name, and the second clause adds a real precondition — the group_id must be a group the current account can access. There is no explicit when-to-use/when-not guidance or routing to alternatives such as get_group_list for discovering valid group numbers.

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