Tools - Boards
Tools for listing boards and getting their column structure. Boards are the central component of the workflow in Almirant: each board contains columns that represent states (Backlog, To Do, In Progress, Review, Testing, Done).
list_boards
Lists all boards in the organization, including area and default status.
Parameters:
This tool requires no parameters.
Example:
{}
Response:
[
{
"id": "b1234567-89ab-cdef-0123-456789abcdef",
"name": "Engineering",
"description": "Main engineering board",
"area": "engineering",
"isDefault": true,
"createdAt": "2025-01-15T10:00:00.000Z",
"updatedAt": "2025-01-15T10:00:00.000Z"
}
]
get_board
Gets a board by its ID, including its columns and the number of work items in each one.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
| id | string (UUID) | Yes | Board ID |
Example:
{
"id": "b1234567-89ab-cdef-0123-456789abcdef"
}
Response:
{
"id": "b1234567-89ab-cdef-0123-456789abcdef",
"name": "Engineering",
"description": "Main engineering board",
"area": "engineering",
"isDefault": true,
"columns": [
{
"id": "col-001",
"name": "Backlog",
"order": 0,
"isDone": false,
"role": "backlog",
"workItemCount": 12
},
{
"id": "col-002",
"name": "To Do",
"order": 1,
"isDone": false,
"role": "todo",
"workItemCount": 5
},
{
"id": "col-003",
"name": "In Progress",
"order": 2,
"isDone": false,
"role": "in_progress",
"workItemCount": 3
},
{
"id": "col-004",
"name": "Review",
"order": 3,
"isDone": false,
"role": "review",
"workItemCount": 2
},
{
"id": "col-005",
"name": "Done",
"order": 4,
"isDone": true,
"role": "done",
"workItemCount": 45
}
]
}
get_board_context
Gets all boards for a project with a semantic column map. The map associates logical roles (backlog, todo, inProgress, review, testing, done) with the corresponding column IDs.
This tool is essential for AI agents to know which column to move a work item to without knowing the exact names of the configured columns.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
| projectId | string (UUID) | No | Project ID (uses the MCP session projectId if omitted) |
Example:
{
"projectId": "550e8400-e29b-41d4-a716-446655440000"
}
Response:
{
"projectId": "550e8400-e29b-41d4-a716-446655440000",
"boards": [
{
"id": "b1234567-89ab-cdef-0123-456789abcdef",
"name": "Engineering",
"area": "engineering",
"columns": [
{ "id": "col-001", "name": "Backlog", "order": 0, "isDone": false, "role": "backlog" },
{ "id": "col-002", "name": "To Do", "order": 1, "isDone": false, "role": "todo" },
{ "id": "col-003", "name": "In Progress", "order": 2, "isDone": false, "role": "in_progress" },
{ "id": "col-004", "name": "Review", "order": 3, "isDone": false, "role": "review" },
{ "id": "col-005", "name": "Testing", "order": 4, "isDone": false, "role": "testing" },
{ "id": "col-006", "name": "Done", "order": 5, "isDone": true, "role": "done" }
],
"columnMap": {
"backlog": "col-001",
"todo": "col-002",
"inProgress": "col-003",
"review": "col-004",
"testing": "col-005",
"done": "col-006"
}
}
]
}
Before moving work items, call get_board_context to obtain the columnMap. Use the map IDs for operations like move_work_item or complete_ai_task without depending on hardcoded column names.
The role mapping works as follows:
- If the column has an explicitly configured
role, that value is used - If not, the role is inferred from the column name (for example, "En Progreso" maps to
in_progress) - Columns that do not match any known pattern are assigned to
otherand do not appear in thecolumnMap