planka_update_task
Update a task by marking it completed or incomplete, and change its order position.
Instructions
Update a task's completion status.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |
Update a task by marking it completed or incomplete, and change its order position.
Update a task's completion status.
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description omits that the tool updates position in addition to completion status. No disclosure of side effects, permissions, or behavior beyond basic update.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence is concise, but lacks necessary detail; could be expanded for clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Incomplete given no output schema and the tool's actual functionality; fails to mention position updates or provide sufficient behavioral info.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Description adds no value beyond schema property descriptions; it even contradicts by implying only completion status, ignoring position.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description claims only updating completion status, but schema includes position parameter. Does not accurately represent the tool's full functionality.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 alternatives like planka_update_card or other task-related tools. Lacks context for appropriate use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/andrejberg/ya-planka-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server