Skip to main content
Glama
Sign In
Task Manager

Task Manager

by vshfrost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

move_task

Idempotent

Moves a task to a specified kanban column or status while enforcing transition rules and WIP limits, so workflow changes stay valid.

Instructions

Перемістити задачу в колонку: status = backlog|todo|blockers|in_progress|in_review|testing|done. Переходи: у todo — лише з testing, in_progress, in_review або blockers (backlog → todo через MCP заборонено, це робить лише Влад на дашборді); у blockers — лише з backlog, todo або testing; у in_progress — лише з todo; у in_review — лише з in_progress; у testing — лише з in_progress, in_review або blockers; у backlog і done — звідки завгодно. З in_progress/in_review у todo задача стає першою в колонці, з testing/blockers — останньою. Перехід у in_progress стереже WIP-ліміт (≤15).

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": {
      "id": "<id>",
      "status": "<status>"
    },
    "name": "move_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations (which only declare non-read-only, idempotent, non-destructive), the description discloses ordering side effects (first vs last position in the column depending on source) and a WIP limit of ≤15 for in_progress. It does not state what happens on a rejected transition (error shape) or the return value, leaving a small gap.

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?

The text is dense but front-loaded, leading with the action and status set before the transition rules. Every clause carries operational information, though the semicolon-chained transition list is somewhat heavy to parse in one pass.

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

Completeness4/5

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

For a two-parameter mutation tool with no output schema, the description covers the critical unknowns: valid statuses, per-target transition constraints, ordering effects, and the WIP cap. Only the failure behavior and response shape are unaddressed, which is a minor omission given the otherwise thorough coverage.

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?

Schema coverage is 0% and the schema declares no enums, so the description carries the full burden: it supplies the complete status value set and the transition semantics that constrain valid values. The 'id' parameter is left undocumented, but its meaning is self-evident, so the compensation is nearly complete.

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 a specific verb and resource ('Перемістити задачу в колонку') and immediately enumerates the exact target statuses (backlog|todo|blockers|in_progress|in_review|testing|done). This makes the tool's scope unmistakable and clearly separates it from siblings like edit_task or add_task, which do not move tasks between columns.

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

Usage Guidelines5/5

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

It spells out the allowed and forbidden transitions per target column, including an explicit prohibition ('backlog → todo через MCP заборонено, це робить лише Влад на дашборді'). An agent knows exactly when a call will succeed and when it must not be attempted, which is stronger than typical when-to-use guidance.

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