nextcloud-mcp

create_task

Create a Nextcloud task with optional due date, list, priority, and description. Keep your to-dos organized directly from the assistant.

Instructions

Create a new task in Nextcloud

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

Input Schema

Name	Required	Description	Default
`due`	No	Due date YYYY-MM-DD (optional)
`listId`	No	List to create in (default: personal)	personal
`summary`	Yes	Task title/summary
`priority`	No	Priority 1-9 where 1 is highest (optional)
`description`	No	Task description (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Aug 2, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Create a new task' implies mutation but does not mention potential side effects, required permissions, default values, or what the response contains. This is insufficient for a creating tool.

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

Conciseness5/5

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

The description is a single, concise sentence that conveys the essential purpose without any filler. It is well-structured and front-loaded.

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?

While the schema thoroughly documents all parameters, the description lacks any detail about return values, error behavior, or side effects. In the absence of an output schema and annotations, the description should provide more context for a mutation tool, making it minimally complete but with clear gaps.

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 100% with each parameter described in the schema. The description itself adds no additional meaning beyond the schema fields, which is acceptable given the complete schema coverage, but it does not reinforce or enhance understanding of any parameters.

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?

The description 'Create a new task in Nextcloud' clearly states the action (create) and the resource (task), and distinguishes it from sibling tools like get_tasks and update_task. It is specific and unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives such as update_task or get_calendar_events. There are no explicit use cases, prerequisites, or exclusion criteria.

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