Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get note

nextcloud_get_note
Read-onlyIdempotent

Retrieve a single Nextcloud note's full content by its ID for reading or processing.

Instructions

Read one note with its content.

GET /index.php/apps/notes/api/v1/notes/{note_id}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "note_id": "<note_id>"
    },
    "name": "nextcloud_get_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idYes

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 readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds only that the full content is returned (useful versus a list view); it says nothing about not-found behavior, permissions, or response shape. With annotations doing the heavy lifting, a 3 is appropriate.

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?

Extremely short and front-loaded, with the purpose in the first sentence. The appended raw endpoint line is marginally useful context rather than wasted space, though it conveys little to an agent that already has the tool.

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 one-parameter read tool with no output schema, the description covers the essentials but leaves gaps: no mention of the returned fields beyond "content", no not-found behavior, and no hint on sourcing note_id. Adequate but not fully self-sufficient.

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 coverage is 0% for the single note_id parameter, so the description carries the burden — but it only embeds {note_id} in a raw REST path. It never states that this is the numeric note identifier nor where to obtain it (e.g., from nextcloud_list_notes), which is the one piece of semantics an agent actually needs.

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 — "Read one note with its content" — which clearly differs from nextcloud_list_notes and the various get_* siblings (get_card, get_contact). It stops short of naming the sibling it complements (list_notes), but the single-note scope is unambiguous.

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?

Usage is only implied: an agent can infer this is for fetching one note when the ID is known. There is no explicit guidance on when to prefer it over nextcloud_list_notes (to discover IDs) or nextcloud_get_properties, and no prerequisites such as the note needing to exist or being accessible.

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