levuvo-nextcloud-mcp

list_files

Read-onlyIdempotent

Lists configured Nextcloud shares or direct entries of a shared folder, enabling step-by-step navigation without accessing the whole account.

Instructions

Levuvo Nextcloud MCP v0.5.3 - List files. List the configured Nextcloud shares, or the direct entries of a shared folder. Use it to navigate the shared folders step by step. Parameters: path (optional) - with an empty path (default) the tool lists ONLY the configured shares (NEXTCLOUD_ALLOWED_PATHS), never the whole Nextcloud account; with a folder path it lists the direct entries of that folder (one level, not recursive), folders first, then by name. limit (1-250, default 100) caps the number of entries. Returns: folder (the listed path, '' for the shares), items (list of entries with path, name, is_dir, size_bytes, content_type, modified, etag, permissions (Nextcloud permission letters of the technical account)) and truncated (true if more entries exist than limit). Excluded entries (NEXTCLOUD_DENIED_PATHS) are never shown. Read-only, no content is downloaded. Errors: a file path fails with 'This is a file. Use get_file_info or read_file.'; folders with more than 2000 entries are rejected; a path that is not shared or explicitly excluded fails with 'The path is not released for the MCP agent.'; malformed paths (leading '/', '..', URL-encoded characters) are rejected; a missing entry fails with 'File or folder not found.'; Nextcloud authentication, network or server problems are reported as errors.

Input Schema

Name	Required	Description	Default
`path`	No	Relative path of a shared folder (or a folder below one), not URL-encoded. Empty (default) = list only the configured shares themselves.
`limit`	No	Maximum number of entries to return (1-250, default 100).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well past the readOnly/idempotent annotations: it discloses the allowed-paths sandbox (never the whole account), the denied-paths exclusion, the 2000-entry folder rejection, the 250 limit with truncation flag, sort order, the permission letters of the technical account, and that no content is downloaded. Error conditions and their exact messages are enumerated.

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?

Front-loaded with the action, then a well-ordered Parameters/Returns/Errors structure with no filler sentences. The only waste is the 'Levuvo Nextcloud MCP v0.5.3 - ' prefix, and the Returns section partially duplicates the existing output schema.

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

Completeness5/5

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

Given a read-only listing tool with four sibling tools and a 2000-entry guard, the description covers scope, recursion depth, ordering, truncation, exclusions, and failure modes. Return values are restated even though an output schema exists, but nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is already 100%, yet the description still adds meaning: the empty path lists only configured shares and never the account root, a folder path lists exactly one level with folders first then by name, and limit drives the truncated flag. The malformed-path rejection rules (leading '/', '..', URL encoding) are additional operational guidance not spelled out in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list files / direct entries of a shared folder) and scopes it to configured Nextcloud shares. The error text explicitly routes file paths to sibling tools get_file_info or read_file, so an agent can separate it from read_file, get_file_info and search_files.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear usage context: 'Use it to navigate the shared folders step by step', and defines the default empty-path behavior versus a folder path (one level, non-recursive). It names alternatives only inside the error message for file paths and never says when search_files would be preferable, so it stops short of full when/when-not guidance.

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

Deploy Server