Skip to main content
Glama
rncz

Nextcloud Notes MCP Server

by rncz

delete_note

Remove a note file from Nextcloud Notes by specifying its filename and optional category, enabling users to delete unwanted notes and manage their note collection.

Instructions

Delete a note file inside Notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
categoryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'delete_note' tool, registered via @mcp.tool() decorator. It constructs the remote path and uses the WebDAV client to delete the note file.
    @mcp.tool()
    def delete_note(filename: str, category: str | None = None) -> str:
        """
        Delete a note file inside Notes.
        """
        full_path = f"Notes/{category}/{filename}" if category else f"Notes/{filename}"
        try:
            client.clean(full_path)
        except Exception as e:
            return f"Failed to delete note: {str(e)}"
        return f"Note deleted successfully: {full_path}"
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action 'Delete' without detailing effects (e.g., permanent deletion, no undo), permissions required, error handling, or output behavior. This is inadequate for a destructive operation with zero annotation coverage.

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 with no wasted words, making it front-loaded and easy to parse. It directly conveys the core action without unnecessary elaboration.

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?

Given the tool's complexity (destructive operation with 2 parameters), lack of annotations, and 0% schema coverage, the description is incomplete. It doesn't address behavioral risks, parameter usage, or output details, even though an output schema exists. More context is needed for safe and effective use.

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%, so the description must compensate by explaining parameters. It adds no meaning beyond the schema, failing to clarify what 'filename' and 'category' represent (e.g., file path, optional category for organization) or how they interact. This leaves parameters undocumented.

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 verb 'Delete' and the resource 'a note file inside Notes', making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'delete_category' or 'rename_note', which would require mentioning it targets individual note files rather than categories or other operations.

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 on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., the note must exist), exclusions (e.g., cannot delete categories), or refer to sibling tools like 'delete_category' for different deletion contexts, leaving usage ambiguous.

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