Skip to main content
Glama

rename_flash_file

Renames a flash-transfer file set by fileset_id, letting you replace its current name with a new accessible name for your account.

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>",
      "new_name": "<new_name>"
    },
    "name": "rename_flash_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_nameYes
fileset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and '重命名' is consistent with that mutation profile, so no contradiction exists. Beyond annotations, the description adds a scoping constraint (the fileset must belong to the current account), but says nothing about name collisions, overwrite behavior, or whether the rename applies to the whole fileset.

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?

A single front-loaded sentence with the action and resource first and the parameter sourcing second; no filler or repetition. It is dense but every clause carries information.

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 two-parameter mutation with no output schema, the definition covers how to obtain the ID but leaves out what is returned, what happens on name conflict, and what errors are possible. Adequate to invoke, incomplete for predicting the result.

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 description coverage is 0%, so the description carries the burden. It does a good job on fileset_id by naming three tools that produce it, but adds nothing about new_name beyond the schema's minLength=1 — no character restrictions, length limits, or handling of duplicate names.

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?

Opens with a specific verb+resource pair ('重命名闪传文件'), which is enough to tell it apart from the sibling rename_group_file / rename_group_file_folder tools by resource type. It stops short of explicitly contrasting with those siblings, so it is clear but not fully differentiated.

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?

The description gives the provenance of fileset_id (create_flash_task, get_fileset_id, list_filesets) and notes the fileset must be accessible to the current account, which implies the right calling context. It offers no when-not conditions and never names a sibling alternative for renaming group files, so usage is implied rather than spelled out.

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