Skip to main content
Glama

create_flash_task

Creates a flash transfer task to send selected files through QQ, with an optional task name and thumbnail path.

Instructions

创建闪传任务 示例路径位于 SnowLuma 服务端,须替换为该服务可读取的实际文件。 files 不能为空。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_flash_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
filesNo路径、{ file, name },或它们的数组
thumb_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare the write/openWorld/non-destructive profile, so the description's value is in the non-obvious gotcha it discloses: the sample path lives on the SnowLuma server and must be replaced with a file the service can actually read — i.e., paths are resolved server-side, not client-side. That is genuinely useful context an agent could not infer. It stops short of 5 because it says nothing about what the task returns, permissions, or what happens on a bad path.

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?

Three short sentences, front-loaded with the purpose and then the two input caveats. No padding; the only weakness is that the sentences are unpunctuated fragments that read as one run-on block.

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 3-parameter, no-output-schema mutation tool with openWorld access, the definition covers the highest-risk ambiguity (path resolution and empty files) but leaves two parameters and the result of the call unexplained. Adequate to invoke correctly in the happy path, incomplete for edge cases.

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

Parameters3/5

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

Schema coverage is only 33% — just `files` is described inline. The description does add real meaning for that parameter (non-empty requirement, server-readable path, and implicitly that the example path is a placeholder), which partially compensates. But `name` and `thumb_path` remain undocumented in both schema and description.

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 (创建闪传任务 = create a flash-transfer task), which is distinguishable from the file-listing/renaming/deleting siblings by name. It does not explicitly contrast itself with create_group_file_folder, 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 Guidelines2/5

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

No statement of when to use this versus the related flash-file tools (get_flash_file_list, send_flash_msg, create_group_file_folder) or what prerequisites exist. The only constraint given is a precondition on input ('files cannot be empty'), which is data validation rather than usage routing.

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