Skip to main content
Glama
rncz

Nextcloud Notes MCP Server

by rncz

create_note

Create a new Markdown note in Nextcloud Notes with optional category organization for structured storage.

Instructions

Create a new Markdown (.md) note.

- If category is None → stored in /Notes/<filename>
- If category is provided → stored in /Notes/<category>/<filename>

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
contentYes
categoryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'create_note' tool. It creates a new Markdown note in Nextcloud via WebDAV, optionally in a category folder, using a temporary local file for upload.
    @mcp.tool()
    def create_note(filename: str, content: str, category: str | None = None) -> str:
        """
        Create a new Markdown (.md) note.
    
        - If category is None → stored in /Notes/<filename>
        - If category is provided → stored in /Notes/<category>/<filename>
        """
        # Determine full paths
        if category:
            full_dir = f"/Notes/{category}"
            full_path = f"{full_dir}/{filename}"
            _ensure_remote_dir(full_dir)
        else:
            full_path = f"/Notes/{filename}"
    
        tmp_path = os.path.join(tempfile.gettempdir(), next(tempfile._get_candidate_names()) + ".tmp")
        with open(tmp_path, "w", encoding="utf-8") as f:
            f.write(content)
    
        client.upload_sync(remote_path=full_path, local_path=tmp_path)
        os.remove(tmp_path)
        return f"Note created successfully: {full_path}"
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 key behavioral traits: it creates a file with Markdown format and specifies storage paths based on category. However, it doesn't mention permissions, error handling, or what happens if a file already exists, leaving gaps for a mutation tool.

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 front-loaded with the core purpose, followed by bullet points that efficiently explain storage rules without wasted words. Every sentence earns its place by adding actionable information, making it appropriately sized and structured.

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 moderate complexity (3 parameters, no annotations, but with an output schema), the description is fairly complete. It covers the creation action and storage logic, but lacks details on permissions or error cases. The output schema likely handles return values, so this isn't a major gap, but more behavioral context would enhance completeness.

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 schema description coverage is 0%, so the description must compensate. It adds significant meaning beyond the schema by explaining how 'category' affects storage paths (e.g., '/Notes/<filename>' vs. '/Notes/<category>/<filename>'), which clarifies parameter impact. It doesn't detail 'filename' or 'content' specifics, but the path logic is crucial and well-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?

The description clearly states the action ('Create a new Markdown (.md) note') and resource ('note'), making the purpose immediately understandable. It distinguishes from siblings like 'edit_note' or 'delete_note' by specifying creation. However, it doesn't explicitly differentiate from 'rename_note' in terms of file creation vs. modification, keeping it from a perfect score.

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?

The description implies usage through the storage rules (e.g., when to use category vs. not), but doesn't explicitly state when to choose this tool over alternatives like 'edit_note' for updates or 'ensure_notes_folder_exists' for setup. It provides context for parameter usage but lacks clear when/when-not guidance relative to siblings.

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