nextcloud_read_fileDownloads a Nextcloud file by path so you can access its contents locally. Use it to retrieve documents, attachments, or other stored files for processing.
Download a file.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes |
Changes observed during successful MCP inspections.
v2.3.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say what is returned (raw bytes, base64, text), how large files or binaries are handled, or what errors occur for a missing path or a directory. With annotations carrying the safety story, the remaining burden was return/content behavior, and it is unaddressed.
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?
Two words are technically efficient and front-loaded with the verb, but the brevity here is under-specification rather than conciseness. A little more text on path format and return type would earn its place.
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?
For a one-parameter read tool with rich annotations and no output schema, the description should at minimum pin down path semantics and what the caller receives. Neither is present, so an agent knows the intent but not how to call it correctly or consume the result.
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?
The single required parameter 'path' has 0% schema description coverage, so the description must explain it and does not. It never says whether the path is absolute, relative to the user's root, whether a leading slash is required, whether directories are accepted, or how special characters are escaped.
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?
"Download a file" names a specific verb and resource, so the basic action is clear. However, it does nothing to distinguish this from siblings like nextcloud_list_files, nextcloud_get_properties, or nextcloud_write_file, leaving the agent to infer that this is the content-retrieval counterpart to the listing and writing tools.
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?
There is no guidance on when to use this tool versus nextcloud_list_files (to discover paths) or nextcloud_get_properties (for metadata only). No prerequisites, no mention that a path must first be obtained, and no exclusions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.