nc-mcp-server

list_directory

Read-onlyIdempotent

List files and folders inside a Nextcloud directory, using path and pagination to manage large result sets.

Instructions

List files and folders in a Nextcloud directory.

Args: path: Directory path relative to user's root (default: "/" for root). Example: "Documents", "Photos/Vacation" limit: Maximum number of entries to return (1-500, default 50). offset: Number of entries to skip for pagination (default 0).

Returns: JSON with "data" (list of entries with path, is_directory, size, etc.) and "pagination" (count, offset, limit, has_more).

Input Schema

TableJSON Schema

Name	Required	Default
`path`	No	/
`limit`	No
`offset`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context beyond annotations: path is relative to the user's root, pagination uses offset/limit with has_more, and the output structure is described.

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

Conciseness5/5

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

The description is well-structured with a clear purpose line followed by concise Args and Returns sections. Every line adds necessary information, and the most important behavioral details are front-loaded.

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?

For a simple read-only directory listing tool, the description covers all parameters, defaults, pagination behavior, and the return shape. Since annotations and an output schema also exist, nothing essential is missing for an agent to call it correctly.

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

Parameters5/5

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

The input schema has zero property descriptions, so the description carries the full burden. It fully compensates by explaining path semantics with examples, the valid range for limit (1-500), and the purpose of offset for pagination.

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?

The description opens with a specific verb and resource: 'List files and folders in a Nextcloud directory.' This clearly identifies the operation and distinguishes it from sibling file tools such as search_files, get_file, and upload_file.

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?

Usage context is implied by the first sentence and the parameter explanations, but there is no explicit guidance about when to choose this tool over alternatives like search_files or list_trash. A clear 'use this for directory browsing, not search' statement would strengthen it.

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

Deploy Server