Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List tasks

nextcloud_list_tasks
Read-onlyIdempotent

List VTODO tasks from a specified Nextcloud calendar, optionally including completed tasks, to review and manage calendar to-dos.

Instructions

List the tasks (VTODO) of one task-capable calendar.

REPORT /remote.php/dav/calendars/{user}/{calendar}

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": {
      "calendar_url": "<calendar_url>"
    },
    "name": "nextcloud_list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
calendar_urlYes
include_completedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so safety behavior is covered. The description adds only a raw DAV REPORT endpoint string, which is implementation detail rather than agent-relevant behavior; it says nothing about return shape, task ordering, paging, or why a non-task calendar would fail.

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

Conciseness3/5

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

Two short lines with no filler, but the second line is an unexplained URL/verb fragment that reads like internal documentation and is not front-loaded as actionable guidance. Nothing is padded, yet the structure does not prioritize what the caller needs first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description is the only place to learn what a returned task looks like (UID, summary, due, status, completion) and whether completed tasks appear by default. It supplies none of that, leaving a listing tool under-described for an agent that must interpret results.

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%, so the description carries the burden. The '/remote.php/dav/calendars/{user}/{calendar}' template does add concrete meaning to the required calendar_url beyond 'type: string', but include_completed is never mentioned — the agent must infer from the name and default that it toggles completed-task filtering.

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+resource ('List the tasks (VTODO)') and scopes it to 'one task-capable calendar', which implicitly separates it from nextcloud_list_events on non-task calendars. It never names a sibling explicitly, so differentiation is left partly to inference.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of how to obtain the required calendar_url (e.g. via nextcloud_list_calendars), and no exclusions versus nextcloud_list_events or nextcloud_get_calendar_object. The phrase 'task-capable calendar' hints at a prerequisite but does not state one.

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