atlas-mcp-server
by cyanheads
Verified
get_tasks_by_status
Find tasks with a specific execution status.
When to Use:
- Identifying work in progress
- Finding blocked tasks
- Verifying completed work
- Planning next actions
Best Practices:
- Check BLOCKED tasks for dependency issues
- Monitor IN_PROGRESS tasks for updates
- Review COMPLETED tasks for verification
- Use with path patterns for focused queries
Example: { "status": "BLOCKED", "pathPattern": "project/backend/*", "reasoning": "Checking for blocked backend tasks to identify and resolve dependencies. This helps maintain project momentum by addressing bottlenecks early." }
Input Schema
Name | Required | Description | Default |
---|---|---|---|
pathPattern | No | Optional glob pattern to focus search: - Use * for single segment wildcard - Use ** for recursive wildcard - Examples: - project/* (direct children) - project/backend/** (all backend tasks) - */security/* (security tasks at any level) Note: Combines with status filter for precise queries | |
status | Yes | Status to filter tasks by: - PENDING: Not yet started tasks - IN_PROGRESS: Active work items - COMPLETED: Successfully finished tasks - BLOCKED: Tasks waiting on dependencies - CANCELLED: Discontinued tasks Note: Returns all tasks in given status regardless of hierarchy |