Skip to main content
Glama
Nextcloud MCP Server

Nextcloud MCP Server

by stack74

File or folder details

nextcloud_get_file_info
Read-onlyIdempotent

Retrieve details for a Nextcloud file or folder, including size, type, modified date, owner, permissions, sharing status, file ID, and a web link.

Instructions

Details of one file or folder: size, type, last modified, owner, permissions, favorite/shared flags, file ID and a link that opens it in the Nextcloud web interface.

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_get_file_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFile or folder path, relative to the user's Nextcloud root, e.g. '/Documents/Offers/offer-4711.pdf'
response_formatNo'markdown' for readable output, 'json' for structured datamarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value on top by enumerating the returned attributes, including permissions, favorite/shared flags, and the web-UI link, which tells the agent what data it can rely on. It stops short of noting behavior for missing paths or permission errors, so it is not a 5.

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?

A single dense sentence with the verb and subject front-loaded ('Details of one file or folder') followed by the field list. No filler, no repetition of the title, nothing that could be cut.

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?

There is no output schema, so the description must carry the return-value burden, and the field enumeration does that adequately for a simple two-parameter getter whose annotations cover safety. Minor gap: it doesn't say what happens when the path does not exist.

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 100%: the schema documents 'path' with an example and explains the markdown/json enum for 'response_format'. The description adds no parameter-level detail beyond that, so the baseline of 3 applies.

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?

The description names a specific resource (one file or folder) and enumerates exactly what it returns: size, type, last modified, owner, permissions, favorite/shared flags, file ID and a web link. That makes the purpose unmistakable and implicitly separates it from content-returning siblings like nextcloud_read_file or nextcloud_download_file, though it never names an alternative.

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 explicit when-to-use or when-not-to-use guidance. The agent must infer from 'one file or folder' that this is a metadata lookup for a known path, and is given no signal about choosing between this, nextcloud_list_files, or the search tools when it doesn't yet have a path.

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