Skip to main content
Glama

put_fs_tasks_id

Update an existing file system task (copy, move, delete, etc.) by its ID, modifying its state, progress, or other properties.

Instructions

Updates the FsTask task with the given id

Error codes: invalid_id, path_not_found, internal_error, disk_unavailable, invalid_request, invalid_conflict_mode, exec_failed, out_of_memory, task_not_found, invalid_state, invalid_task_type, destination_conflict, access_denied, disk_full, none, archive_read_failed, archive_open_failed, archive_write_failed, chdir_failed, dest_is_not_dir, file_exists, file_not_found, mkdir_failed, open_input_failed, open_output_failed, opendir_failed, overwrite_failed, path_too_big, repair_failed, rmdir_failed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id__pathYes(Path parameter)
idNoid
typeNoThe valid task types are: — Values: `cat`: Concatenate multiple files; `cp`: Copy files; `mv`: Move files; `rm`: Remove files; `archive`: Creates an archive; `extract`: Extract an archive; `repair`: Check and repair files
stateNoValues: `queued`: Queued (only one task is active at a given time); `running`: Running; `paused`: Paused (user suspended); `done`: Done; `failed`: Failed (see error)
errorNoValues: `none`: No error; `archive_read_failed`: Error reading archive; `archive_open_failed`: Error opening archive; `archive_write_failed`: Error writing archive; `chdir_failed`: Error changing directory; `dest_is_not_dir`: The destination is not a directory; `file_exists`: File already exists; `file_not_found`: File not found; `mkdir_failed`: Unable to create directory; `open_input_failed`: Error opening input file; `open_output_failed`: Error opening output file; `opendir_failed`: Error opening directory; `overwrite_failed`: Error overwriting file; `path_too_big`: Path is too long; `repair_failed`: Failed to repair corrupted files; `rmdir_failed`: Error removing directory; `same_file`: Source and Destination are the same file; `unlink_failed`: Error removing file; `unsupported_file_type`: This file type is not supported; `write_failed`: Error writing file; `disk_full`: Disk is full; `internal`: Internal error; `invalid_format`: Invalid file format (corrupted ?); `incorrect_password`: Invalid or missing password for extraction; `permission_denied`: Permission denied; `readlink_failed`: Failed to read the target of a symbolic link; `symlink_failed`: Failed to create a symbolic link
created_tsNotask creation timestamp — Unix timestamp (seconds since epoch).
started_tsNotask start timestamp — Unix timestamp (seconds since epoch).
done_tsNotask end timestamp — Unix timestamp (seconds since epoch).
durationNotask duration in seconds
progressNotask progress in percent (scaled by 100)
etaNoestimated time remaining before the task completion (in seconds)
fromNocurrent source file (if available)
toNocurrent destination file (if available)
nfilesNonumber of files to process
nfiles_doneNonumber of files processed
total_bytesNototal bytes to process
total_bytes_doneNonumber of bytes processed
curr_bytesNosize of the file currently processed
curr_bytes_doneNonumber of bytes processed for the current file
rateNoprocessing rate in byte/s

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

The description lists many error codes, which hint at failure modes, but does not disclose side effects, prerequisites, or behavioral traits like authorization requirements or state transitions. With no annotations, the description fails to adequately convey behavioral transparency.

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

Conciseness2/5

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

The core statement is concise but is followed by an extensive, redundant list of error codes that duplicates information in the input schema. This reduces conciseness and adds clutter without new value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (20 parameters) and the presence of an output schema, the description should provide more context about typical usage, effects of updating different fields, and relationship to other task operations. It falls short.

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?

Input schema coverage is 100%, so the baseline is 3. The description does not add extra meaning beyond the schema; it only repeats error codes that already exist in the parameter descriptions.

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 clearly states the tool updates an existing FsTask resource, distinguishing it from read (get_fs_tasks_id), delete (delete_fs_tasks_id), and creation (post_fs_*) siblings. However, it does not elaborate on which fields are updatable beyond the input schema.

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 guidance is provided on when to use this tool versus alternatives. Sibling tools exist for creating, reading, and deleting tasks, but the description lacks context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nelson-PROIA/freebox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server