Skip to main content
Glama

get_essence_msg_list

Read-only

Retrieves a QQ group's essence message list by group ID, helping you find highlighted messages and important discussions.

Instructions

获取精华消息列表 将 group_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>"
    },
    "name": "get_essence_msg_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the access restriction that group_id must be a group the current account can reach, which is genuinely new information. It says nothing about ordering, size limits, or pagination of the returned list.

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?

Two short clauses, with the action stated first and the parameter note second. Nothing is padded, though the second sentence reads as a terse instruction rather than integrated guidance.

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 one-parameter read tool with no output schema, the bar is low, and the description covers what it fetches and the access constraint. It leaves the agent guessing about result ordering, volume, and whether the response is paginated.

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 there is a single required parameter whose meaning ('群号') is already documented in the schema. The description's 'replace with a group number accessible to the current account' adds a constraint on which values are valid, which is a modest but real increment over the 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 states a specific verb and resource ('获取精华消息列表' — get the pinned/essence message list), which cleanly distinguishes it from the sibling mutators delete_essence_msg and set_essence_msg. It stops short of naming those siblings as alternatives, so it is clear but not fully differentiated.

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?

Usage is only implied: the reader infers this is the read path for a group's essence messages. The second clause adds a real precondition (the group must be accessible with the current account), but there is no explicit statement of when to pick this over get_group_msg_history or get_msg.

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