Skip to main content
Glama

Desktop: Filesystem

desktop_filesystem
Destructive

Perform file system operations—read, write, copy, move, delete, list, search, or inspect files and directories—using absolute paths for local automation.

Instructions

Manage file system operations with eight modes: 'read' (read text file contents with optional 1-based line offset/limit), 'write' (create or overwrite a file; set append=true to append), 'copy' (copy file or directory to destination), 'move' (move or rename file/directory), 'delete' (delete file or directory; set recursive=true for non-empty dirs), 'list' (list directory contents with optional glob pattern filter), 'search' (find files matching a glob pattern under a root directory), 'info' (get file/directory metadata: size, dates, type). Use absolute paths. Relative paths are NOT supported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesOperation mode.
pathYesAbsolute path to the file or directory to operate on.
limitNoMaximum number of lines to return (read mode).
appendNoAppend to file instead of overwriting (write mode).
offsetNo1-based starting line number for read mode.
contentNoText content to write (required for write mode).
patternNoGlob pattern to filter (required for search; optional for list).
encodingNoText encoding for read/write operations.utf-8
overwriteNoAllow overwriting existing destination (copy, move).
recursiveNoRecurse into sub-directories (list, search, delete).
destinationNoDestination path (required for copy and move modes).
show_hiddenNoInclude hidden files/dirs starting with '.' (list mode).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered and the description is consistent with it (write/move/delete are indeed mutations). The description adds real behavioral context beyond the annotations: append=true to append, recursive=true required for non-empty directory deletion, and overwrite semantics for copy/move. It does not cover permissions or error behavior, so not a 5.

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 dense paragraph that front-loads the purpose and then enumerates modes efficiently; no filler sentences. It would read better as a structured list given eight modes, but every clause carries information and nothing is wasted.

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 12-parameter tool with no output schema, the description covers all modes and the key path constraint, and annotations carry the mutation/destructive profile. Return values are not described, but no output schema exists to offload them and the description does not claim to; completeness is strong, though error/permission behavior is absent.

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 100%, so the baseline is 3. The description reinforces several parameters (offset/limit for read, append for write, recursive for delete, glob pattern for list/search, metadata fields for info), but most of this duplicates the schema text rather than adding new semantics. Cross-mode relationships (which param belongs to which mode) are its main added 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 states a clear verb and resource ('Manage file system operations') and enumerates all eight modes with a concrete gloss of each ('read', 'write', 'copy', 'move', 'delete', 'list', 'search', 'info'). An agent can tell exactly what this tool does. It does not, however, differentiate itself from overlapping siblings such as desktop_tree (directory browsing) or desktop_find (file search), which caps it below 5.

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 per-mode glosses imply when each mode applies, and the closing constraint ('Use absolute paths. Relative paths are NOT supported') is a genuinely useful usage rule. But there is no explicit when-to-use-vs-alternatives guidance (e.g. when to use 'search' versus desktop_find, or 'list' versus desktop_tree), and no exclusions. Adequate but with clear gaps.

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