Skip to main content
Glama

get_flash_file_list

Retrieves the file list for a specified flash-transfer fileset using its fileset_id, which you can obtain from task or fileset lookup tools.

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

Input Schema

NameRequiredDescriptionDefault
fileset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare destructiveHint=false and openWorldHint=true, but the description adds no behavioral context beyond them – no pagination, ordering, size limits, or what the returned list entries contain. There is also mild tension: a 'get list' description sits alongside readOnlyHint=false, which the description neither explains nor reconciles.

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 with the purpose front-loaded and the parameter provenance immediately after; nothing is redundant. The final instruction ('replace with an accessible fileset') is slightly ambiguous in phrasing but costs little space.

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 one-parameter list tool with no output schema, the description covers purpose and parameter sourcing, which is the core need. It leaves out what the list looks like and whether results are scoped/paged, and it does not explain the non-read-only annotation, so an agent still has 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% (the single property only declares type/minLength), so the description must carry the meaning – and it does, explaining the provenance of fileset_id and the account-access constraint on valid values. That is substantially more than the schema provides, though it omits any format or example value.

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 opens with a specific verb+resource pair ('获取闪传文件列表' – get the flash-transfer file list), which is unambiguous about what is returned. It does not explicitly differentiate itself from siblings like get_flash_file_url or delete_flash_file, but the resource scope is clear enough for selection.

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 genuine prerequisite guidance by naming the three tools that produce a valid fileset_id (create_flash_task, get_fileset_id, list_filesets) and noting the fileset must belong to the current account. It stops short of saying when to use this list versus the URL/metadata siblings, so guidance is implied rather than complete.

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