Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List notifications

nextcloud_list_notifications
Read-onlyIdempotent

Retrieve all current account notifications to review alerts and updates. Use it to check pending notifications and act on Nextcloud events.

Instructions

List the account's current notifications.

GET /ocs/v2.php/apps/notifications/api/v2/notifications

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_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds nothing behavioral beyond a raw OCS endpoint path: it does not say whether results are paginated, whether dismissed items are excluded, or what state the account must be in.

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?

One clear sentence with the scope up front, followed by the endpoint. The endpoint line is the only questionable content, since an agent gains little from the raw URL, but nothing is bloated.

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?

With zero parameters and rich annotations, the main open question is what a notification contains and whether the list is bounded. There is no output schema to cover that, and the description does not describe the returned fields or whether the list is complete or paged, leaving a modest 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 tool takes zero parameters, so there is no parameter meaning for the description to supply; the baseline for a no-parameter tool applies.

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 gives a specific verb and resource: it lists the account's current notifications. The word "current" distinguishes it from the dismissal sibling and from nextcloud_list_activities, though neither sibling is named explicitly.

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 implied by "current notifications" (active/unread items rather than history) and by the contrast with nextcloud_dismiss_notification, but the description never states when to reach for this tool rather than list_activities or a dismiss call, and it gives no prerequisites.

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