Skip to main content
Glama

get_group_info

Read-only

Retrieves QQ group information by group ID for the current account, with an option to skip cached data.

Instructions

获取群信息 将 group_id 替换为当前账号可访问的群号。 Returns: 群信息对象。

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

Input Schema

NameRequiredDescriptionDefault
group_idYes群号
no_cacheNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/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 safety is covered structurally. Beyond that the description adds only "Returns: 群信息对象", with no indication of what fields are returned or how the no_cache flag changes behavior (caching, freshness, rate limits).

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?

Very short and front-loaded: purpose first, then parameter guidance, then return note. No filler, though the terseness comes at the cost of substance rather than being efficient with it.

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 simple two-parameter read tool this covers the minimum: what it fetches and the access precondition. It is incomplete in that the returned object's contents are unnamed and no_cache is left unexplained, which matters given there is no output schema.

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 documented as "群号", no_cache undocumented). The description adds real meaning for group_id by requiring it to be a group the current account can access, but says nothing about no_cache, so it only partially compensates for the gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"获取群信息" gives a verb and a resource, but the resource ("group info") is generic and is not distinguished from the closely named siblings get_group_detail_info and get_group_info_ex. An agent cannot tell from the text which of the three returns what.

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?

The only guidance is "将 group_id 替换为当前账号可访问的群号", which is a parameter-filling instruction plus an implicit access precondition. There is no statement about when to prefer this tool over the sibling info tools, and no exclusions.

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