Skip to main content
Glama

set_group_todo

Sets a group to-do from a real, queryable message_id that belongs to the target group, enabling a specific group message to be marked as a task.

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

Input Schema

NameRequiredDescriptionDefault
group_idYes群号
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this as a non-destructive write (readOnlyHint=false, destructiveHint=false, openWorldHint=true). The description goes beyond that by disclosing the message-existence precondition and the non-obvious rule that negative message_id values are legal, which is exactly the kind of behavioral context annotation hints cannot convey.

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 purpose is front-loaded in the first clause, and every following clause carries a real constraint. It reads as a run-on separated by semicolons rather than clean sentences, which slightly hurts scanability but wastes no words.

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 tool with annotations and no output schema, the description covers the main failure modes (invalid or foreign message_id). It is silent on the success outcome and on how this interacts with the cancel/complete todo siblings, leaving a modest 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 50% — only group_id is described ('群号'), and message_id has no schema description. The description compensates strongly for message_id (real id from events/results, negatives legal, must exist in storage, must belong to this group), but adds nothing about the group_id parameter, so it is solid rather than complete.

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 opening phrase '设置群待办' states a specific verb (set) and resource (group todo), so the agent can immediately tell what the tool does. It does not explicitly distinguish itself from siblings such as cancel_group_todo or complete_group_todo, which keeps it short of a 5.

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 description gives concrete preconditions for a valid call: the message must be a real message_id from a message event or send result, must be queryable in the current account's message storage, and must belong to the group. However, it never states when to prefer this over the closely related cancel/complete/list todo tools, so guidance is implied rather than explicit.

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