Skip to main content
Glama
rncz

Nextcloud Notes MCP Server

by rncz

delete_category

Remove a category folder from Nextcloud Notes to organize your notes by deleting unwanted or obsolete categories.

Instructions

Delete a category folder inside Notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
category_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The delete_category tool handler function, decorated with @mcp.tool() which handles both definition and registration. It deletes the specified category folder using the WebDAV client.
    @mcp.tool()
    def delete_category(category_name: str) -> str:
        """
        Delete a category folder inside Notes.
        """
        full_path = f"Notes/{category_name}"
        try:
            client.clean(full_path)  # works for folders too
        except Exception as e:
            return f"Failed to delete category: {str(e)}"
        return f"Category deleted successfully: {full_path}"
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Delete' implies a destructive operation, but the description doesn't specify whether this is permanent, reversible, what happens to notes within the category, or what permissions are required. For a destructive operation with zero annotation coverage, this is a significant gap in behavioral transparency.

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 - a single sentence with zero wasted words. It's front-loaded with the core action and target. While it may be too brief for completeness, as a standalone statement it's efficiently structured.

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

Completeness2/5

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

For a destructive operation with no annotations, 0% schema coverage, and multiple sibling tools, the description is inadequate. While an output schema exists (which helps with return values), the description doesn't address critical context like what 'delete' means operationally, how it differs from related tools, or parameter requirements. A deletion tool needs more contextual information than this provides.

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

Parameters2/5

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

Schema description coverage is 0%, meaning the single parameter 'category_name' has no documentation in the schema. The description provides no additional information about this parameter - it doesn't explain what constitutes a valid category name, whether case matters, or how to reference existing categories. The description fails to compensate for the complete lack of schema documentation.

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 ('Delete') and target ('a category folder inside Notes'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from similar sibling tools like 'edit_category' or 'delete_note' - it only tells what it does, not how it differs from alternatives.

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?

The description provides no guidance about when to use this tool versus alternatives. With sibling tools like 'edit_category', 'delete_note', and 'list_categories', there's no indication of when deletion is appropriate versus editing or when to check what categories exist first. No prerequisites or exclusions are mentioned.

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