Skip to main content
Glama
rncz

Nextcloud Notes MCP Server

by rncz

ensure_notes_folder_exists

Create the /Notes folder in Nextcloud if it doesn't exist, ensuring a location for storing notes.

Instructions

Ensure that the /Notes folder exists in Nextcloud. Creates it if it doesn't exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the ensure_notes_folder_exists tool. It is decorated with @mcp.tool(), which registers it with the MCP server. The function calls the helper _ensure_remote_dir to create the /Notes folder if it does not exist.
    def ensure_notes_folder_exists() -> str:
        """
        Ensure that the /Notes folder exists in Nextcloud.
        Creates it if it doesn't exist.
        """
        _ensure_remote_dir("/Notes")
        return "/Notes folder exists or created successfully."
  • Helper function used by the ensure_notes_folder_exists tool to create a remote directory using the WebDAV client, ignoring if it already exists.
    def _ensure_remote_dir(path: str):
        """Ensure that a remote directory exists in Nextcloud."""
        try:
            client.mkdir(path)
        except Exception:
            # Folder probably already exists → ignore
            pass
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the key behavioral trait (conditional creation) and the target resource, but does not mention authentication requirements, error handling, or what 'exists' means (e.g., permissions, exact path). It adds some value but lacks comprehensive behavioral details.

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?

The description is extremely concise with two sentences that are front-loaded and waste no words. Every sentence earns its place by stating the purpose and the conditional action directly.

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?

Given the tool's simplicity (0 parameters, no annotations, but has an output schema), the description is complete enough for basic understanding. It covers what the tool does and its conditional behavior. However, it could benefit from mentioning the output or any side effects for full completeness, though the output schema mitigates this gap.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details, which is appropriate. A baseline of 4 is applied as it correctly avoids redundancy, though it doesn't enhance parameter understanding beyond the schema.

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?

The description clearly states the tool's purpose with a specific verb ('ensure exists') and resource ('/Notes folder in Nextcloud'), and distinguishes it from siblings like create_category or create_note by focusing on a specific system folder. It explicitly mentions the conditional creation behavior.

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

Usage Guidelines4/5

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

The description implies usage context ('if it doesn't exist') but does not explicitly state when to use this tool versus alternatives like checking folder existence manually or using other folder management tools. It provides clear intent but lacks explicit comparison to sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rncz/nextcloud-notes-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server