Umaku

Showing 25 of 44 from the live probe.

• Organizations List

  List all organisations the authenticated user belongs to. Returns each organisation's id and name. Call this to resolve the organisation ID needed by `projects_list`.

• Organizations Get

  Get full details of a single organisation.

• Projects My Access

  List all projects the authenticated user can access across all organisations. Call this first to discover available project IDs before using other tools.

• Projects List

  List projects in an organisation, with optional filters.

• Projects Get

  Get full project details: name, description, status, tech stack, charter, milestones, and feedback history. Note: member list is not included in this response. Use `projects_get_members` to fetch the full member list with roles. The feedback_history field contains agentic feedback reports. Each report is one of four types: - sprint_inclusion: sprint planning and task inclusion analysis - bugs_finder: automated bug detection report - code_quality: code quality assessment - devops_compli

• Projects Get Dashboard

  Get project dashboard: sprint metrics, completion percentage, and timeline.

• Projects Get Members

  List all members of a project with their roles and user IDs. This is the correct tool to use when you need to resolve a person's name to a user ID — for assigning tasks or bugs, or for @mentions in comments. It is scoped to the project and accessible to all project members.

• Projects Get Descoped Tasks

  Get the list of pending agentic descope requests for a project. During a sprint, the agentic service analyses task progress and flags incomplete tasks it believes should be descoped (e.g. not enough progress, blocked, or unlikely to finish). Each flagged task becomes a descope request that a PM must act on: - Accept: moves the task to the 'Descoped' column in the BACKLOG sprint - Reject: dismisses the request, task stays in its current sprint This endpoint returns the tasks currently pend

• Sprints List

  List sprints for a project. Each sprint includes name, goal, dates, status, and progress percentage. Every project has a built-in sprint named 'BACKLOG' (status: 'planning'). It is a permanent container for unassigned or descoped tasks — it never starts or completes. Exclude it when showing sprint progress to users. Completed sprints include an agentic feedback field with up to four reports: - sprint_inclusion: sprint planning and task inclusion analysis - bugs_finder: automated bug detect

• Sprints Get Active

  Get the currently active sprint for a project. Returns the sprint with its goal, dates, and progress. Returns an empty list if no sprint is currently active.

• Sprints Get

  Get full sprint details: goal, dates, status, progress percentage, total/completed task counts, and feedback for completed sprints.

• Sprints Get Timeline

  Get timeline visualization data for all sprints in a project. Similar to Jira's timeline view. Returns all sprints (BACKLOG excluded) with their tasks and calculated timeline boundaries: - timeline_start: earliest task start_date in the sprint - timeline_end: latest task end_date in the sprint - tasks: minimal task data (name, start_date, end_date, column) Useful for understanding the project schedule and identifying sprints or tasks that have no dates set.

• Sprints Move Tasks

  Move one or more kanban tasks to a different sprint. All tasks and the target sprint must belong to the same project. Column assignment is automatic based on the move direction: - Backlog → regular sprint: task column is set to 'TODO' - Regular sprint → backlog: task column is set to 'In Planning' - Regular sprint → regular sprint: task column is unchanged The BACKLOG is a special built-in sprint that always exists for every project. It holds unassigned or descoped tasks. To move tasks

• Kanban Get Board

  Get the full kanban board for a project: all columns and their tasks. IMPORTANT: sprint_ids is required to see tasks. If omitted, the board returns the column structure only — all task lists will be empty. Use `sprints_get_active` first to get the active sprint ID, then pass it here to see the current work. Tasks in the BACKLOG sprint (the built-in unassigned/descoped container) can be retrieved by passing the BACKLOG sprint ID. Get it from `sprints_list` — it's the sprint named 'BACKLOG' with

• Kanban Create Task

  Create a new task in a kanban column. The description field is rendered in a rich text editor — always write it as HTML. For developer tasks use this structure: <h3>User Story</h3> <p>As a [role], I want [goal] so that [reason].</p> <h3>Acceptance Criteria</h3> <ul> <li>criterion 1</li> <li>criterion 2</li> </ul>

• Kanban Update Task

  Update one or more fields of a kanban task. Only provided fields are changed. The description field is rendered in a rich text editor — write it as HTML.

• Kanban Move Task

  Move a task to a different column and/or position.

• Kanban Delete Task

  Permanently delete a kanban task. This cannot be undone.

• Bugs List

  List bugs for a project. Each bug includes title, severity, status, days_open, and comment count.

• Bugs Get

  Get full bug details: title, description, steps to reproduce, severity, status, assignee, linked commits, and days open.

• Bugs Create

  Report a new bug on a project.

• Bugs Update

  Update one or more fields of a bug. Only provided fields are changed.

• Comments List

  List all comments on a kanban task, bug, or project. Returns threaded comments with reporter info and reply counts. Results are cursor-paginated, newest first (20 per page by default). The response includes 'next' and 'previous' cursor URLs for navigation, plus 'has_next' and 'has_previous' flags. Pass the 'cursor' value from a 'next' link to fetch the next page.

• Comments Create

  Add a comment to a kanban task, bug, or project. Supports threaded replies. When mentioning users, always use their numeric ID in the message text (e.g. '@123'), not their username. This ensures the mention stays correct even if the user later changes their username. Use projects_get_members to resolve a name to an ID before composing the message. Every mentioned user must also appear in the mentioned_users list so the backend can validate and display the current username.

• Comments Update

  Edit the text of an existing comment. Only the comment author can edit. When mentioning users, always use their numeric ID in the message text (e.g. '@123'), not their username. This ensures the mention stays correct even if the user later changes their username. Use projects_get_members to resolve a name to an ID before composing the message. Every mentioned user must also appear in the mentioned_users list so the backend can validate and display the current username.