Skip to main content
Glama

vikunja_tasks

Create, update, delete, assign, comment, attach files, set reminders, apply labels, and bulk manage tasks in Vikunja. Organize projects and track progress with comprehensive operations.

Instructions

Manage tasks with comprehensive operations (create, update, delete, list, assign, attach files, comment, bulk operations)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subcommandYes
titleNo
descriptionNo
projectIdNo
dueDateNo
priorityNo
labelsNo
assigneesNo
repeatAfterNo
repeatModeNo
idNo
filterNo
filterIdNo
pageNo
perPageNo
sortNo
searchNo
allProjectsNo
doneNo
commentNo
commentIdNo
taskIdsNo
fieldNo
valueNo
tasksNo
reminderDateNo
reminderIdNo
otherTaskIdNo
relationKindNo
sessionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are provided, and the description gives no behavioral traits (e.g., idempotency, side effects, permissions). The tool could be destructive or require specific conditions, but nothing is disclosed.

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?

The description is concise with one sentence, but it sacrifices substance for brevity. It is not verbose, but it fails to provide necessary details.

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

Completeness1/5

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

Given the 30 parameters, 22 subcommands, and numerous sibling tools, the description is critically incomplete. It lacks parameter explanations, output schema, and usage context, leaving the agent severely underinformed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no information about the 30 parameters. Parameters like subcommand, id, and filters are left unexplained, making it impossible for an agent to use them correctly.

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

Purpose3/5

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

The description states the tool manages tasks with comprehensive operations, but it does not clarify how it differs from specialized siblings like vikunja_task_assignees, vikunja_task_crud, etc. The purpose is vague and overlapping.

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 on when to use this tool versus sibling tools. There is no mention of alternatives or exclusions, leaving the agent to guess the appropriate context.

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