Skip to main content
Glama

get_fileset_id

Read-only

Extracts the fileset ID from a QQ Flash Transfer share code or official qfile.qq.com share link, resolving the share_code input so you can reference the file set in follow-up operations.

Instructions

从 QQ 闪传分享码或官方分享链接获取 fileset_id share_code 使用实际闪传分享链接或提取码。 Returns: { fileset_id }:解析出的文件集 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": {
      "share_code": "<share_code>"
    },
    "name": "get_fileset_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
share_codeYesQQ 闪传分享码,或 https://qfile.qq.com/q/... 官方分享链接

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 agent knows this is a safe networked read. The description adds only the output shape ({ fileset_id }); it says nothing about behavior on invalid or expired share codes, redirect handling, or whether authentication is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and purpose-first with a clearly labeled return value, which is good. However, the middle fragment is a garbled sentence in mixed Chinese/English that duplicates the schema rather than contributing information, hurting readability.

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?

For a one-parameter resolver with no output schema, the definition covers purpose, accepted input forms, and the returned field, which is roughly enough to call it correctly. Missing details about failure modes for malformed codes and the need to feed the resulting id into downstream tools are minor but real gaps.

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 100% and the single parameter already documents both accepted forms (a share code or a https://qfile.qq.com/q/... link). The description's fragment 'share_code 使用实际闪传分享链接或提取码' merely restates that, adding no new meaning such as format validation or precedence rules.

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 (获取/parse) and resource (fileset_id) plus the source (QQ 闪传 share code or official share link), and it names the return value { fileset_id }. It does not distinguish this resolver from siblings such as get_fileset_info or download_fileset, so an agent cannot tell from the text alone which step comes first in the workflow.

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?

Usage is only implied: the agent can infer it is the right tool when it holds a share code/link and needs an internal fileset_id. There is no explicit when-not case, no statement that other tools require the resulting id, and no guidance on sequencing versus get_fileset_info.

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