Skip to main content
Glama
rncz

Nextcloud Notes MCP Server

by rncz

create_category

Create a new category in Nextcloud Notes by generating a subdirectory to organize your notes efficiently.

Instructions

Create a new category inside Notes by creating a subdirectory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
category_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The create_category tool handler, decorated with @mcp.tool(). Creates a category by ensuring the remote directory /Notes/{category_name} exists.
    @mcp.tool()
    def create_category(category_name: str) -> str:
        """
        Create a new category inside Notes by creating a subdirectory.
        """
        full_path = f"Notes/{category_name}"
        _ensure_remote_dir(full_path)
        return f"Category created successfully: {full_path}"
  • _ensure_remote_dir helper function called by create_category to create the category directory if it doesn't exist.
    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
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'creating a subdirectory', which hints at a mutation operation, but doesn't disclose behavioral traits like permissions needed, whether it overwrites existing categories, error handling, or rate limits. This leaves significant gaps for a tool that modifies data.

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 a single, efficient sentence that front-loads the purpose ('Create a new category') and adds clarifying detail ('inside Notes by creating a subdirectory'). Every word earns its place with no redundancy or fluff.

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?

Given the tool has 1 parameter, no annotations, and an output schema exists (which covers return values), the description is minimally adequate. However, as a mutation tool with no behavioral disclosure, it lacks completeness regarding how the operation works, potential side effects, or integration with sibling tools like 'list_categories'.

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 doesn't add any meaning beyond the schema, which only shows 'category_name' as a required string. No details on format, constraints, or examples are provided. With 1 parameter and no schema descriptions, the baseline is 3 as it doesn't worsen understanding but adds no value.

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 category') and the resource ('inside Notes'), with the specific mechanism 'by creating a subdirectory'. It distinguishes from siblings like 'edit_category' or 'delete_category' by specifying creation. However, it doesn't explicitly contrast with 'ensure_notes_folder_exists', which might be related.

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?

No explicit guidance on when to use this tool versus alternatives like 'edit_category' for modifying existing categories or 'ensure_notes_folder_exists' for setup. The description implies usage for creating new categories but lacks context on prerequisites, such as whether the parent directory must exist.

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