Skip to main content
Glama

complete_group_todo

Marks a group todo as completed by providing the group ID and a valid message ID that belongs to the group's message history.

Instructions

完成群待办 使用消息事件或发送结果中的真实 message_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>",
      "message_id": "<message_id>"
    },
    "name": "complete_group_todo"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes群号
message_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 declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds non-obvious behavioral constraints the annotations cannot convey: negative message_ids are legal, the message must be retrievable in the current account's store, and it must belong to the target group. It does not say what state change occurs or whether completion is reversible.

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?

The description is compact and front-loads the action before the constraints. Sentences are dense but each carries a distinct validation rule; minor cost is the run-on punctuation between clauses.

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 two-parameter mutation with no output schema, the description covers the critical invocation constraint (valid, belonging message_id) but omits what completing the todo changes, error conditions when the message is missing, and idempotency behavior on repeat calls.

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 only 50% (only group_id carries a description), but the description compensates by documenting the message_id contract in detail — sourced from message events or send results, negative values accepted, must be queryable, must match the group. That meaningfully exceeds what the bare schema provides.

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 ("完成群待办" / complete a group todo) that is clearly distinct from the sibling set_todo and cancel_todo operations. It doesn't explicitly contrast itself with cancel_group_todo, but the action is unambiguous.

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?

It states prerequisites (must use a real message_id from an event or send result, message must be queryable in the account's store, must belong to this group), which implicitly defines when the call will succeed. There is no explicit when-to-use guidance relative to cancel_group_todo or set_group_todo.

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