Skip to main content
Glama
rncz

Nextcloud Notes MCP Server

by rncz

list_categories

Retrieve all note categories (directories) from the Nextcloud Notes folder to organize and manage your notes effectively.

Instructions

List all categories (directories) inside /Notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'list_categories' tool. It uses the WebDAV client to list items in the /Notes directory and filters out .md files to return only category directories.
    @mcp.tool()
    def list_categories() -> List[str]:
        """
        List all categories (directories) inside /Notes.
        """
        items = client.list("/Notes")
        # Keep only directories (exclude .md files)
        return [f for f in items if not f.endswith('.md')]
Behavior2/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. It states what the tool does but lacks behavioral details such as whether it requires authentication, how it handles errors (e.g., if /Notes doesn't exist), the format of the output (though an output schema exists), or any rate limits. This is a significant gap for a tool 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 zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly.

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's low complexity (0 parameters, output schema provided), the description is minimally adequate. However, with no annotations and missing behavioral context (e.g., error handling, prerequisites), it leaves gaps that could hinder an agent's correct invocation, especially for edge cases like missing directories.

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 tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics beyond the schema, but with no parameters, a baseline of 4 is appropriate as it doesn't need to compensate for gaps.

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 ('List all categories') and the resource ('directories inside /Notes'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'list_notes_of_a_category' or 'list_uncategorized_notes', which also list content but with different scopes.

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., whether /Notes must exist), exclusions, or comparisons to siblings like 'list_notes_of_a_category' for listing notes within a specific category.

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