Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Create task

nextcloud_create_task
Idempotent

Creates a single VTODO task in a task-capable Nextcloud calendar with a summary, due date, priority, and description.

Instructions

Create one task (VTODO) in a task-capable calendar (the Tasks app shows it).

PUT /remote.php/dav/calendars/{user}/{calendar}/{uid}.ics

priority follows iCalendar: 1 highest, 9 lowest, 0 undefined.

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>",
      "summary": "<summary>"
    },
    "name": "nextcloud_create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNo
summaryYes
priorityNo
descriptionNo
calendar_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the write/idempotent/non-destructive profile, so the description's real contribution is the capability constraint that the target calendar must be task-capable and the disclosure that the object lands at a DAV path ending in {uid}.ics. That tells the agent the main silent-failure mode (writing to a non-task calendar). It stops short of saying how errors surface or whether the uid is generated server-side.

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?

Front-loaded with the core action, then the endpoint, then the priority caveat — no filler sentences. The raw DAV path line is somewhat technical but does convey the storage shape, so it earns a place; overall the block is tight.

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 5-parameter mutation tool with no output schema and no parameter documentation in the schema, the definition covers purpose and priority but leaves the accepted `due` encoding and the source/format of `calendar_url` unspecified. No return-value explanation is required since there is no output schema, but the input gaps are real for a create operation.

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?

With 0% schema description coverage the description must carry the load, and it only fully explains `priority` (1 highest, 9 lowest, 0 undefined) while indirectly constraining `calendar_url` to a task-capable calendar. The `due` parameter has a bare union type with no format documented (ISO 8601? date vs datetime? timezone?), and `description` gets nothing beyond its name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create one task (VTODO)') and pins down the object type with the iCalendar VTODO term, which implicitly separates it from nextcloud_create_event (VEVENT in a calendar) and from the list/update task siblings. An agent can tell what is being written and where without opening the schema.

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 by the parenthetical 'the Tasks app shows it' and 'task-capable calendar', which hints the calendar must support tasks but never says how to obtain such a calendar_url (e.g., via nextcloud_list_calendars) or what to do if none exists. No explicit when-not or alternative-tool routing is given.

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