Skip to main content
Glama

List notes

nextcloud_list_notes
Read-onlyIdempotent

List a Nextcloud account's notes, optionally filtered by category, so you can browse or locate stored notes.

Instructions

List the account's notes, optionally of one category.

GET /index.php/apps/notes/api/v1/notes

Tool call template

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": "nextcloud_list_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered and the description rightly doesn't repeat it. What it adds is limited to the raw endpoint path, with no disclosure of ordering, result size, or whether an unknown category yields an empty list or an error.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short lines, front-loaded with the purpose and no repetition of annotations or schema. The trailing 'GET /index.php/apps/notes/api/v1/notes' is implementation detail an agent cannot act on, which keeps it just short of a 5.

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?

For a simple single-parameter list tool with full annotation coverage and no output schema, the definition is serviceable. It is still thin on what a returned note contains and whether results are bounded, which matters for an unfiltered listing of an entire account.

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

Parameters3/5

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

Schema description coverage is 0% and the single 'category' parameter has no description or enum in the schema, so the description carries the burden. Saying 'optionally of one category' does establish that the parameter is a category filter and that omitting it returns all notes, but exact-match versus prefix semantics and valid values remain undefined.

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?

States a specific verb and resource ('List the account's notes') plus an optional scope qualifier ('optionally of one category'), which lets an agent separate it from nextcloud_get_note and nextcloud_create_note. It never names a sibling explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

'Optionally of one category' implies the filtered-listing use case, but there is no explicit when-to-use guidance, no statement that it is the enumeration counterpart to nextcloud_get_note, and no note about paging or when the result set is too large.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools