Skip to main content
Glama

Get properties

nextcloud_get_properties
Read-onlyIdempotent

Retrieve a Nextcloud file or folder's size, type, etag, and file ID by path to inspect metadata before managing or sharing it.

Instructions

Read the properties of one file or folder (size, type, etag, file id).

PROPFIND /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_get_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.0
    • removedInput schema / properties / path / default
      Removed value: -""
    • addedInput schema / required
      Added value: +[
      +  "path"
      +]
  2. First observedv2.3.4

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds the returned property set and reveals the underlying PROPFIND call, but says nothing about behavior for missing/inaccessible paths, permissions, or auth requirements.

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

Conciseness4/5

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

Two short lines with the purpose front-loaded and no filler. The raw PROPFIND endpoint line is useful to some agents but is borderline technical noise for others.

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 simple one-parameter read tool with full annotations and no output schema, the description is nearly sufficient: it enumerates the returned fields, which substitutes for an output schema. Only the path-format and error-case details remain unstated.

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

Parameters4/5

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

Schema coverage is 0% and the single 'path' parameter is undocumented, but the endpoint template '/remote.php/dav/files/{user}/{path}' conveys that the path is relative to the user's files root — meaningful context the schema lacks. It still doesn't specify leading-slash or encoding conventions.

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?

States a specific verb (Read) and resource (properties of one file or folder) and enumerates what comes back (size, type, etag, file id). The word 'one' distinguishes it from bulk tools like nextcloud_list_files and from content reads like nextcloud_read_file, though no sibling is named explicitly.

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 is only implied: an agent can infer this is the metadata call rather than a listing or content read, but the description never says when to prefer it over nextcloud_list_files or nextcloud_search_files, nor any prerequisites (e.g. the item must exist).

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