Skip to main content
Glama
rncz

Nextcloud Notes MCP Server

by rncz

list_uncategorized_notes

Retrieve Markdown files from the main Notes folder to identify unorganized documents for categorization and management.

Instructions

List all Markdown (.md) files directly inside /Notes (not in subfolders).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'list_uncategorized_notes' tool. It lists Markdown files directly in the /Notes directory using the WebDAV client. The @mcp.tool() decorator registers it as an MCP tool.
    @mcp.tool()
    def list_uncategorized_notes() -> List[str]:
        """
        List all Markdown (.md) files directly inside /Notes (not in subfolders).
        """
        items = client.list("/Notes")
        return [f for f in items if f.endswith('.md')]
Behavior3/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 discloses the tool's scope and file type filtering, which is useful behavioral context. However, it does not mention potential outputs, error conditions, or other behavioral traits like performance or limitations.

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 key information with zero waste. It uses clear language and is appropriately sized for the tool's simplicity.

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 low complexity (0 parameters, no annotations, but with an output schema), the description is mostly complete. It explains what the tool does and its scope. However, it could benefit from mentioning the output format or any constraints, though the output schema mitigates this gap.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details, which is appropriate. Baseline is 4 for 0 parameters, as it avoids redundancy.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('List'), resource ('Markdown (.md) files'), and scope ('directly inside /Notes, not in subfolders'). It distinguishes itself from sibling tools like 'list_categories' and 'list_notes_of_a_category' by focusing on uncategorized files in the root directory.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by specifying 'directly inside /Notes (not in subfolders)', which helps differentiate it from tools that might list files recursively or in categories. However, it does not explicitly state when to use this tool versus alternatives like 'list_notes_of_a_category' or provide exclusions.

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