Retrieve all notes from Nextcloud Notes app. Use optional limit parameter to control the number of notes returned.
Retrieve all notes from Nextcloud Notes app
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_notes"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations present, the description carries the full burden of behavioral disclosure. It only says 'retrieve all notes' without explaining whether it returns metadata or full content, whether pagination applies beyond the limit parameter, or what fields appear in the response. These are significant gaps for a list operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that directly states the action and target. It is efficient with no wasted words, though slightly too sparse to fully support the other dimensions.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity, the description still misses key contextual details: the return format (list of metadata vs. full content), whether the limit parameter applies to the response, and how this relates to the sibling get_note_content tool. This incompleteness could lead to incorrect assumptions.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not mention the 'limit' parameter at all. The parameter name is somewhat self-explanatory, but the description fails to clarify that 'limit' controls the maximum number of notes returned or how the default of 50 behaves. The description does not compensate for the lack of schema documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves all notes from the Nextcloud Notes app, using a specific verb and resource. It distinguishes from the sibling get_note_content by indicating a bulk operation ('all notes'), though it does not explicitly name alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool versus alternatives like get_note_content or create_note. The description neither specifies exclusions nor mentions context preferences, leaving the agent to infer from the name and sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.