Skip to main content
Glama

get_group_honor_info

Read-only

Retrieve QQ group honor details by group ID and optional category; unrequested categories return empty arrays, and the current Dragon King value may be null.

Instructions

获取群荣誉信息 未请求的分类仍返回空数组;当前龙王可能为 null。

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_group_honor_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 does add genuine behavioral context beyond them: unrequested categories yield empty arrays (so empty does not mean absent) and the current "dragon king" field may be null. Still, nothing is said about permissions or response shape.

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 sentences, front-loaded with the purpose and followed by a caveat about return values; nothing is redundant. It is almost too terse, but every clause carries information.

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?

With no output schema, the description must carry return-value semantics, and it does so only for two edge cases (empty arrays, null dragon king). The undefined category values for `type` remain an unresolved gap for a two-parameter call.

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%: group_id is documented as "群号" in the schema, but the `type` parameter has no description and no enum. "未请求的分类" vaguely tells the agent that `type` selects categories, yet no valid category values are given, so it only marginally compensates for the gap.

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, "获取群荣誉信息" (get group honor info), which tells the agent exactly what resource is retrieved. It does not distinguish itself from similarly-named siblings like get_group_info_ex or get_group_detail_info, so it stops short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives, nor any prerequisites or exclusions. The note about unrequested categories implies a category-scoped call is possible, but that is incidental rather than explicit guidance.

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