nextcloud_list_contentsLists files and folders in a Nextcloud directory using PROPFIND so you can inspect or navigate storage contents by path.
List files and folders in a directory using PROPFIND.
| Name | Required | Description | Default |
|---|---|---|---|
| path | No |
Changes observed during successful MCP inspections.
v2.3.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and openWorld, so the safety profile is covered. The description adds only the protocol name (PROPFIND), without explaining depth/recursion behavior, whether properties are returned, or how large listings are handled — the details an agent actually needs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One short sentence, front-loaded with the verb and resource, with no filler. Brevity is appropriate here; the issue is missing content, not verbosity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so the description is the only place to learn what a listing returns, and it says nothing. Combined with an undocumented path parameter, an agent lacks the information needed to call this reliably against the right sibling.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for the single `path` parameter, so the description must compensate and does not. It never says whether path is absolute or relative to the user root, what the empty-string default means, or what format (slash-prefixed, URL-encoded) is expected.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a concrete verb and resource ("List files and folders in a directory"), so the purpose is understandable. But it never differentiates itself from the very similar sibling nextcloud_list_files, leaving an agent unable to pick between the two from the description alone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use, when-not-to-use, or named alternative is given. With siblings like nextcloud_list_files and nextcloud_get_properties in the catalog, the absence of routing guidance is a real gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.