Update sprint MCP tools for labels param + todo item_type #12

New issue

Closed

opened 2026-03-06 13:32:48 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-06 13:32:48 +00:00

Owner

Plan

todo-sprint-item-labels-and-todo-type -- MCP tool counterpart to pal-e-docs #70

Repo

forgejo_admin/pal-e-docs-mcp

User Story

As Betty Sue
I want add_sprint_item and move_sprint_item MCP tools to support a labels parameter and todo as a valid item_type
So that I can classify sprint items and track ad-hoc work via MCP

Context

The pal-e-docs backend (issue #70) is adding a labels column to sprint items and todo as a new item_type. The MCP tools need to expose these new capabilities so Betty Sue can use them. This PR deploys after the backend PR.

File Targets

Files the agent should modify:

src/pal_e_docs_mcp/tools/sprints.py -- add labels param to add/move tools, update item_type descriptions

Files the agent should NOT touch:

Any backend files -- those are in pal-e-docs repo

Acceptance Criteria

add_sprint_item accepts optional labels: str | None param with Field description
move_sprint_item accepts optional labels: str | None param with Field description
All item_type Field descriptions include 'todo' as a valid value
get_sprint_board description mentions todo board

Test Expectations

No tests to run -- MCP tool definitions are declarative
Verify: tool signatures match the backend API contract

Constraints

Follow existing param patterns in sprints.py (Annotated with Field)
labels param description: "Comma-separated labels, e.g. 'type:bug,scope:unplanned'"
Do NOT access pal-e-docs MCP tools

Checklist

PR opened
No unrelated changes

project-pal-e-sprints -- sprint management project
pal-e-docs #70 -- backend counterpart (must deploy first)

### Plan `todo-sprint-item-labels-and-todo-type` -- MCP tool counterpart to pal-e-docs #70 ### Repo `forgejo_admin/pal-e-docs-mcp` ### User Story As Betty Sue I want `add_sprint_item` and `move_sprint_item` MCP tools to support a `labels` parameter and `todo` as a valid `item_type` So that I can classify sprint items and track ad-hoc work via MCP ### Context The pal-e-docs backend (issue #70) is adding a `labels` column to sprint items and `todo` as a new item_type. The MCP tools need to expose these new capabilities so Betty Sue can use them. This PR deploys after the backend PR. ### File Targets Files the agent should modify: - `src/pal_e_docs_mcp/tools/sprints.py` -- add labels param to add/move tools, update item_type descriptions Files the agent should NOT touch: - Any backend files -- those are in pal-e-docs repo ### Acceptance Criteria - [ ] `add_sprint_item` accepts optional `labels: str | None` param with Field description - [ ] `move_sprint_item` accepts optional `labels: str | None` param with Field description - [ ] All `item_type` Field descriptions include `'todo'` as a valid value - [ ] `get_sprint_board` description mentions todo board ### Test Expectations - [ ] No tests to run -- MCP tool definitions are declarative - Verify: tool signatures match the backend API contract ### Constraints - Follow existing param patterns in sprints.py (Annotated with Field) - labels param description: `"Comma-separated labels, e.g. 'type:bug,scope:unplanned'"` - Do NOT access pal-e-docs MCP tools ### Checklist - [ ] PR opened - [ ] No unrelated changes ### Related - `project-pal-e-sprints` -- sprint management project - pal-e-docs #70 -- backend counterpart (must deploy first)