Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search files

nextcloud_search_files
Read-onlyIdempotent

Search Nextcloud files by case-insensitive name substring within a folder, optionally filter by MIME type, and return relative paths for locating files.

Instructions

Search files by name (case-insensitive substring) under one folder.

SEARCH /remote.php/dav

mime_prefix narrows to a content type family, for example image/ or video/. Returns paths relative to the account root.

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": {
      "query": "<query>"
    },
    "name": "nextcloud_search_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
limitNo
queryYes
mime_prefixNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: matching is case-insensitive substring, scope is limited to one folder, and results are paths relative to the account root.

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

Conciseness3/5

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

Purpose is front-loaded and the sentences are short, but the standalone "SEARCH /remote.php/dav" line is internal HTTP detail that gives an agent nothing actionable, and the mime_prefix note is oddly placed after it rather than with the core behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the brief return note (paths relative to account root) is helpful, but key ambiguities remain for a search tool: whether "under one folder" is recursive into subfolders, and how limit interacts with the total result set. Adequate but not fully complete.

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 description must compensate: it explains query (name substring, case-insensitive) and mime_prefix (content-type family with image/ and video/ examples). It leaves limit (default 50, max?) and the exact meaning/format of path under-explained.

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 and resource with its matching semantics: "Search files by name (case-insensitive substring) under one folder." That scope implicitly separates it from a plain listing, but the description never names the obvious sibling nextcloud_list_files, so an agent must infer the distinction.

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, and no mention of alternatives such as nextcloud_list_files for browsing or nextcloud_read_file for retrieving contents. Only a weak hint (match by name substring) suggests the intended use case.

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