Skip to main content
Glama

Read file

nextcloud_read_file
Read-onlyIdempotent

Download a specific file from Nextcloud by path and return its contents base64-encoded, enabling retrieval for processing, backup, or transfer.

Instructions

Download one file; the bytes come back base64-encoded.

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "nextcloud_read_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.4

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description earns credit for adding the return-format behavior (raw bytes arrive base64-encoded), which matters because there is no output schema; it does not cover size limits or error behavior for a missing path.

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?

Two short lines, front-loaded with the action and the return encoding, with the endpoint appended as reference. No filler or repetition.

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?

For a one-parameter read tool with no output schema and safety fully covered by annotations, the definition supplies the essential missing piece (base64 return value). It falls short only on path format conventions and failure behavior for nonexistent files.

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 description coverage is 0%, so the single `path` parameter is undocumented in structured fields; the DAV template `files/{user}/{path}` hints that path is relative to a user's file root, but it never states the expected format, leading slash conventions, or encoding. Partial compensation for the coverage gap.

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 ('Download one file') and adds a distinguishing detail — the payload is base64-encoded bytes — plus the underlying DAV endpoint. An agent can tell this apart from nextcloud_list_files or nextcloud_search_files without inspecting schemas.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says to prefer this over nextcloud_search_files to locate a file, or over nextcloud_get_note for note content, and no prerequisites (existing path, permissions) are stated. The only usage context is implied by the 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