Skip to main content
Glama
megamaced

tasks-mcp

by megamaced
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_task

Create a new task in your Nextcloud Tasks list, with optional due dates, priorities, subtasks, and tags. Returns the stored task with its new uid.

Instructions

Create a task. The list may be omitted when the account has one task list or NEXTCLOUD_DEFAULT_TASK_LIST is set. Returns the task as stored, including its new uid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dueNoDue date: "YYYY-MM-DD" for a whole day, "YYYY-MM-DDTHH:MM:SS" for a local time, or "...Z" for UTC. null removes it.
listNoTask list uri or display name.
startNoStart date, same format as due. null removes it.
pinnedNoNextcloud's pinned flag.
statusNoDefaults to NEEDS-ACTION on a new task.
summaryYesTask title.
locationNoFree-text location. null removes it.
priorityNoRFC 5545 priority: 1 is highest, 9 is lowest, 0 or null means none. The Tasks UI shows 1-4 as high, 5 as medium, 6-9 as low.
parentUidNouid of the parent task, making this a subtask of it. Must be in the same list. null detaches it to the top level.
sortOrderNoManual sort position within the list.
categoriesNoTags, replacing any already set. null or [] removes them all.
descriptionNoLonger notes. null or "" removes them.
dueTimezoneNoIANA zone for a local due time, e.g. "Europe/London". Stored as the equivalent UTC instant. Not valid with a whole-day date or a "Z" time.
hideSubtasksNoCollapse this task's subtasks in the Tasks UI.
startTimezoneNoIANA zone for a local start time.
percentCompleteNoProgress, 0-100. Set automatically to 100 when status becomes COMPLETED.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.5/5.0
Behavior4/5

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

With no output schema, the description usefully states that the tool 'Returns the task as stored, including its new uid,' which an agent would otherwise not know. It also discloses the list-resolution behavior. Annotations already indicate this is not read-only, so the description adds value beyond them without contradiction.

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?

Two sentences, no filler. The core action is front-loaded, followed by the most important optionality rule and the return behavior. Every clause earns its place.

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

Completeness5/5

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

For a 16-parameter tool with no output schema, the description plus the fully documented schema gives an agent everything needed to call it correctly. It covers the required input, the one conditional rule, and the return value.

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 input schema has 100% parameter description coverage, so baseline is 3. The description goes further by explaining when the list field can be omitted, a detail not derivable from the schema alone, making it genuinely additive.

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 opens with the specific verb and resource: 'Create a task.' It also adds creation-specific details (optional list, returned uid), which clearly differentiate it from update_task, complete_task, and delete_task among the siblings.

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

Usage Guidelines4/5

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

It gives an explicit condition for when the list parameter may be omitted: when the account has one task list or NEXTCLOUD_DEFAULT_TASK_LIST is set. This is genuinely useful routing/context for invoking the tool, though it does not discuss alternatives since creation is unambiguous.

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