Skip to main content
Glama

get_group_info_ex

Read-only

Fetches extended information for an accessible QQ group by group_id, optionally bypassing cache to return current group details.

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

Input Schema

NameRequiredDescriptionDefault
group_idYes
no_cacheNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 the safety profile is covered. The description adds only the 'accessible to current account' constraint and says nothing about caching behavior despite exposing a no_cache flag, nor about what information the 'extended' response includes.

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 the constraint. Nothing is padded, but the brevity comes at the cost of substance rather than from tight editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero schema description coverage, no output schema, and multiple closely named siblings, the definition leaves an agent unable to distinguish this tool from get_group_info or to understand no_cache. For a two-parameter tool with an 'extended' variant, substantially more context is required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden. It clarifies group_id only loosely (a group number accessible to the account) and completely ignores no_cache, whose caching semantics are non-obvious and would materially change agent behavior.

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?

The description states a verb and resource ('获取群信息' / get group info) and marks it as '扩展' (extended), but never explains what the extension adds. Siblings such as get_group_info and get_group_detail_info make the distinction critical, and the description gives no basis for choosing among them.

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 when-to-use or when-not-to-use guidance. The only operational note is that group_id must be a group the current account can access, which is a validity constraint rather than routing guidance, and no alternative tool is mentioned.

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