Skip to main content
Glama

get_group_todo_list

Read-only

Retrieves the todo list for a specified QQ group, returning todo items with message identifiers, server summaries, and timestamps so you can review and act on group tasks.

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

Input Schema

NameRequiredDescriptionDefault
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description goes further by disclosing the return payload: an array of todos carrying message identifiers usable for subsequent todo operations, plus a server-side summary and timestamp. That chaining hint is genuine information an agent cannot get from the annotations or the one-parameter schema.

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?

Three short segments: purpose, parameter precondition, return shape — front-loaded and free of filler. The return summary is the only extra, and it 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 one-parameter read tool with no output schema, the description supplies the purpose, the parameter precondition and a sketch of the returned fields, which is enough for correct invocation. Only the absence of any pointer to the related complete/cancel todo tools leaves a minor gap.

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% and the single group_id parameter is already documented with type, minimum and description. The description only adds the accessibility constraint (the group must be visible to the current account), which is a mild but real addition, so baseline 3 is right.

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 opens with a specific verb+resource, '获取群待办列表' (get the group's todo list), which immediately distinguishes it from the mutating siblings set_group_todo, complete_group_todo and cancel_group_todo. It does not explicitly name those alternatives, but the read verb alone is enough to separate it from the write-side tools.

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?

The only guidance is the constraint '将 group_id 替换为当前账号可访问的群号' (use a group number the current account can access), which is a precondition rather than a when-to-use hint. It never says to prefer this over, say, get_group_notice or get_group_msg_history when looking for pending items, so usage is only implied by the tool name.

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