Skip to main content
Glama

cancel_group_todo

Destructive

Cancels a group todo in QQ using a real message_id from message events or send results. The message must belong to the specified group and be queryable in the current account's message store.

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": "cancel_group_todo"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes群号
message_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 destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the mutation risk is conveyed structurally. The description adds genuine context beyond that – the message must exist in the current account's store and belong to the group, and negative IDs are permitted – but it never says whether the cancellation is reversible or what happens to the todo state afterward.

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?

Short and front-loaded with the action first, followed by the message_id sourcing rules. Slightly run-on across three clauses with semicolons, but every clause carries actionable constraint information rather than filler.

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 destructive, open-world mutation with no output schema, the description covers the critical preconditions (message existence, group membership, ID sourcing). It leaves out what the response contains and whether the todo can be restored, which an agent might want before committing to a destructive call.

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% (group_id is described as '群号'; message_id has no schema description). The description compensates by explaining where message_id should come from (message events or send results), that negative values are valid, and that the message must belong to the given group – meaning well beyond the bare schema.

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 names a specific verb+resource ('取消群待办' = cancel group todo), which an agent can immediately distinguish from siblings like complete_group_todo or set_group_todo. It does not explicitly name an alternative, so it falls short of a 5, 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 supplies prerequisites rather than when-to-use guidance: the message_id must come from a real message event or send result, the message must be queryable in the current account's store, and it must belong to the target group. These are useful invocation conditions, but there is no explicit statement of when to choose this over complete_group_todo or other todo operations.

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