Skip to main content
Glama

task_workflow

Sync, approve, clarify, improve clarity, and clean up stale tasks in a unified workflow.

Instructions

[HINT: Task workflow. action=sync|approve|clarify|clarity|cleanup. Manage task lifecycle.]

Unified task workflow tool consolidating sync, approval, clarification, clarity improvement, and stale cleanup.

Actions:

  • action="sync": Sync TODO markdown tables ↔ Todo2

  • action="approve": Bulk approve/move tasks by status

  • action="clarify": Manage task clarifications (sub_action: list|resolve|batch)

  • action="clarity": Improve task clarity (adds estimates, renames, removes dependencies)

  • action="cleanup": Move stale In Progress tasks back to Todo

📊 Output: Workflow operation results 🔧 Side Effects: Modifies task states ⏱️ Typical Runtime: <1 second (most actions)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNo"sync", "approve", "clarify", "clarity", or "cleanup"sync
dry_runNoPreview changes without applying (sync, approve, cleanup)
statusNoFilter tasks by status (approve)Review
new_statusNoTarget status (approve)Todo
clarification_noneNoOnly tasks without clarification (approve)
filter_tagNoFilter by tag (approve)
task_idsNoJSON list of task IDs (approve)
sub_actionNo"list", "resolve", or "batch" (clarify action)list
task_idNoTask to resolve (clarify)
clarification_textNoClarification response (clarify)
decisionNoDecision made (clarify)
decisions_jsonNoBatch decisions as JSON (clarify)
move_to_todoNoMove resolved tasks to Todo (clarify)
auto_applyNoAuto-apply improvements (clarity action)
output_formatNoOutput format (clarity action)text
stale_threshold_hoursNoHours before task is stale (cleanup action)
output_pathNoSave results to file

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It explicitly states side effects ('Modifies task states'), output format, and typical runtime, which gives good transparency about behavior beyond basic functionality.

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 well-structured with a hint, summary, action list, and metadata (output, side effects, runtime). No unnecessary words, and key information is front-loaded. Every sentence serves a purpose.

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?

With 17 parameters and an output schema, the description covers the main actions and side effects. It could be more explicit about parameter dependencies per action, but the schema and action list provide sufficient context for most use cases.

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%, so baseline is 3. The description adds context by grouping parameters under actions (e.g., 'sub_action' for clarify) but does not provide additional semantics beyond what the schema already describes.

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 clearly states it is a unified task workflow tool consolidating sync, approval, clarification, clarity, and cleanup actions. Each action is briefly explained, making the tool's purpose distinct from siblings like task_analysis or task_discovery.

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

Usage Guidelines3/5

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

The description lists actions and their purposes but does not explicitly state when to use this tool versus alternatives. Sibling tools are available but no guidance is provided on choosing between them, leaving usage implied rather than explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidl71/project-management-automation'

If you have feedback or need assistance with the MCP directory API, please join our Discord server