Skip to main content
Glama
rclone-ui

rclone-mcp

by rclone-ui

operations_list

List objects and directories from a remote path, with options for recursion, hashes, and metadata. Returns output like rclone lsjson.

Instructions

List objects — Lists objects and directories for a remote path, returning the same fields as rclone lsjson.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fsNoRemote name or path to list, for example `drive:`.
optNoOptional JSON-encoded object of listing flags (e.g. `{ "recurse": true, "showHash": true }`).
_asyncNoRun the command asynchronously. Returns a job id immediately.
_groupNoAssign the request to a custom stats group.
remoteNoDirectory path within `fs` to list; leave empty to target the root.
recurseNoSet to true to list directories recursively.
dirsOnlyNoSet to true to return only directory entries.
metadataNoSet to true to include backend-provided metadata maps.
showHashNoSet to true to include hash digests for each entry.
filesOnlyNoSet to true to return only file entries.
hashTypesNoSpecify one or more hash algorithms to include when `showHash` is true (e.g. `md5`).
noModTimeNoSet to true to omit modification times for faster listings on some backends.
noMimeTypeNoSet to true to omit MIME type detection.
showOrigIDsNoSet to true to include original backend identifiers where available.
showEncryptedNoSet to true to include encrypted names when using crypt remotes.
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions returning fields like lsjson but does not state that the operation is read-only, nor does it cover side effects, rate limits, or auth requirements. Minimal behavioral insight.

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?

The description is a single sentence that efficiently conveys purpose and output format. While short, it does not waste words.

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?

With 15 parameters and no output schema, the description should explain the return format or pagination. It merely references 'same fields as rclone lsjson' without elaboration, leaving the agent uninformed about the response structure.

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 adds no extra meaning to parameters beyond what the schema already provides.

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 lists objects and directories for a remote path, and references rclone lsjson for output fields. It is specific enough to distinguish from sibling operations tools like operations_stat or operations_size.

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 on when to use this tool versus alternatives, or when not to use it. The description lacks any context for usage decisions.

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/rclone-ui/rclone-mcp'

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