Skip to main content
Glama

set_essence_msg

Marks a QQ message as essence using its actual message_id; the message must 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": {
      "message_id": "<message_id>"
    },
    "name": "set_essence_msg"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is largely covered. The description adds two genuinely behavioral facts not in the annotations: negative message_id values are accepted, and the target must exist in the current account's store. It does not describe failure modes or the effect on an already-essenced message.

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?

One compact sentence with the operation stated first and the two key constraints layered after it via semicolons – front-loaded and waste-free. The trailing clause wording is slightly dense but nothing is redundant.

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 single-parameter mutation with annotations and no output schema, the definition covers the two things an agent could realistically get wrong (where the id comes from, negative-id validity). It does not mention permission requirements beyond the account-store precondition, which is a minor residual gap.

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 description coverage is 0%, so the description carries the full burden for the single parameter, and it does so well: it names the source of a valid value and clarifies that negatives are legal, which the schema only implies via 'not const 0'. It could still say what the id refers to structurally (private vs group context), preventing a higher score.

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 (设置精华消息 = mark a message as 'essence'), which is clearly distinct from the sibling delete_essence_msg and get_essence_msg_list. It does not explicitly name those siblings, but the operation itself 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent where a valid id comes from (a message event or a send result) and adds a real precondition: the message must be retrievable from the current account's message store. What is missing is explicit when-not guidance or a named alternative, so it stops short of a 5.

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