Skip to main content
Glama

get_group_file_system_info

Read-only

Retrieve a QQ group's file storage details—file count, storage limit, and used/total space—by passing an accessible group ID.

Instructions

获取群文件系统信息 将 group_id 替换为当前账号可访问的群号。 Returns: { file_count, limit_count, used_space, total_space }:群文件数量与容量信息(均为服务端实际值)。

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

Input Schema

NameRequiredDescriptionDefault
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/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 value beyond that by spelling out the returned fields (file_count, limit_count, used_space, total_space) and noting they are server-side actual values — important since no output schema exists. No contradiction with the read-only annotation.

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 compact sentences, purpose and return payload front-loaded, with no filler. The phrasing '将 group_id 替换为...' reads slightly like template instruction language rather than documentation prose, but it remains efficient.

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?

This is a simple, single-parameter read-only tool with no output schema, and the description supplies both the access constraint and the shape of the return values. That covers what an agent needs to call it correctly; only a note on error behavior when the group is inaccessible is missing.

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 coverage is 100% and the single parameter already carries a description of '群号'. The description still adds meaning by specifying the group number must be one the current account can access, which is an access-scoping constraint not present in 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+resource: retrieve the group file system info (file count and capacity) for a given group. It is clearly distinct from listed siblings such as get_group_files_by_folder or get_group_file_url, but it never explicitly names or contrasts an alternative, so it stops short of a 5.

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?

It gives one practical prerequisite — substitute a group_id that the current account can actually access — which is useful context. However, there is no explicit when-to-use / when-not-to-use guidance or named alternative for listing files versus fetching quota information, leaving the agent to infer usage.

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