Skip to main content
Glama

get_fileset_info

Retrieve metadata and details for a QQ fileset using its fileset_id, obtained from create_flash_task, get_fileset_id, or list_filesets, to inspect a fileset your account can access.

Instructions

获取文件集信息 fileset_id 来自 create_flash_task、get_fileset_id 或 list_filesets,替换为当前账号可访问的文件集。

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": {
      "fileset_id": "<fileset_id>"
    },
    "name": "get_fileset_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=false and openWorldHint=true, yet the description never explains why a 'get' operation is not read-only, nor what happens on the call. The only behavioral value added is the constraint that the fileset must be accessible to the current account, which is useful but thin for a tool flagged as non-read-only and open-world.

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, front-loaded with the purpose, with no filler. The phrasing of the second clause ('替换为当前账号可访问的文件集') is slightly awkward but conveys a real constraint efficiently.

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 single-parameter read tool with no output schema, the description should indicate what information is returned, but '文件集信息' stays generic. Combined with the unexplained non-read-only annotation, the definition is adequate but leaves real gaps.

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 0% and the single parameter has no description in the schema, so the description carries the burden – and it does: it identifies where fileset_id originates and constrains it to filesets accessible to the current account. It stops short of stating the expected format, but the sourcing guidance is the substantive gap it fills.

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 gives a specific verb and resource ('获取文件集信息' – retrieve fileset information), which is clearly distinguishable from siblings such as list_filesets or get_fileset_id. It does not explicitly contrast itself with those siblings' behavior, so it falls 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 Guidelines4/5

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

It tells the agent where the required fileset_id must come from (create_flash_task, get_fileset_id, list_filesets), which effectively routes the agent to the right upstream tools. It gives no explicit 'when not to use' or exclusion criteria, so it is clear context rather than full 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