Skip to main content
Glama

List files

nextcloud_list_files
Read-onlyIdempotent

Lists files and folders in a specified Nextcloud directory to browse and manage cloud storage contents.

Instructions

List the files and folders in one folder (PROPFIND, depth 1).

PROPFIND /remote.php/dav/files/{user}/{path}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nextcloud_list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.4

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile needs no restating. The description does add genuinely useful behavior beyond that: depth 1 means children only, no recursion. The raw PROPFIND line is more implementation trivia than agent-relevant behavior, and nothing is said about result ordering, metadata returned, or how large folders behave.

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 core behavior is front-loaded in a single tight sentence with zero filler. The second line is a bare endpoint template that is compact but cryptic to an agent that does not reason in WebDAV terms, so it borders on noise rather than earning its place.

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?

Missing, no output schema, so a note on the shape of the returned listing would have helped; the empty-path-means-root default is also left unexplained. Against that, annotations are rich and the folder-scoping constraint is clear, so an agent can call this correctly with only minor guesswork.

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 coverage is 0% for the single parameter, so the description carries the burden, and it only partially does: the URL template implies path is relative to the user's file root, but neither the description nor the schema explains that the default empty string means the root folder, or whether a leading slash is expected. The one clarifying detail present is that the path identifies a folder, not a file.

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?

States a specific verb and resource ("List the files and folders") and constrains scope to "one folder (PROPFIND, depth 1)", which implicitly separates it from recursive search_files and content-reading read_file. It stops short of naming a sibling explicitly, so the differentiation must be inferred from the depth-1 qualifier.

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 depth-1 wording implies when this tool is appropriate (browsing a single directory) versus a recursive search, but no alternative tool is named and no exclusion is stated. There is no guidance on what to do when the caller does not know the path or wants to find a file by name.

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