Update sprint MCP tools for repo/project boards + needs_approval column #10

New issue

Closed

opened 2026-03-03 04:04:34 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-03 04:04:34 +00:00

Owner

Plan

plan-2026-03-01-pal-e-sprints -- Sprint system expansion (MCP side)

Repo

forgejo_admin/pal-e-docs-mcp

User Story

As Betty Sue (main session agent)
I want the sprint MCP tools to accept the new item_types (repo, project) and column (needs_approval)
So that I can manage all five sprint boards and the full seven-column workflow via MCP

Context

pal-e-docs issue #66 adds repo and project item_types plus needs_approval column to the API. The MCP tools need their descriptions and validation updated to match.

The API itself is generic — it already passes item_type and column through to the API. The changes here are primarily tool description updates so agents know the new options exist, plus any client-side validation that restricts values.

File Targets

Files the agent should modify:

src/pal_e_docs_mcp/tools/sprints.py (or wherever sprint tools are defined) -- Update tool descriptions to list all five item_types and seven columns. Update any Literal/enum validation on the client side.

Files the agent should NOT touch:

Server configuration, authentication, or non-sprint tools.

Acceptance Criteria

add_sprint_item tool description lists repo and project as valid item_types
get_sprint_board tool description lists repo and project as valid item_types
move_sprint_item tool description lists needs_approval as a valid column
add_sprint_item tool description lists needs_approval as a valid column
Any client-side validation accepts the new values

Test Expectations

Verify tool descriptions include new values (manual or automated)
Run command: pytest or manual MCP tool invocation test

Constraints

Depends on pal-e-docs #66 landing first (API must accept new values before MCP sends them)
Match existing tool description patterns

Checklist

PR opened
Tests pass
No unrelated changes

project-pal-e-sprints -- project this affects
pal-e-docs #66 -- API-side changes (dependency)

### Plan `plan-2026-03-01-pal-e-sprints` -- Sprint system expansion (MCP side) ### Repo `forgejo_admin/pal-e-docs-mcp` ### User Story As Betty Sue (main session agent) I want the sprint MCP tools to accept the new item_types (repo, project) and column (needs_approval) So that I can manage all five sprint boards and the full seven-column workflow via MCP ### Context pal-e-docs issue #66 adds `repo` and `project` item_types plus `needs_approval` column to the API. The MCP tools need their descriptions and validation updated to match. The API itself is generic — it already passes item_type and column through to the API. The changes here are primarily tool description updates so agents know the new options exist, plus any client-side validation that restricts values. ### File Targets Files the agent should modify: - `src/pal_e_docs_mcp/tools/sprints.py` (or wherever sprint tools are defined) -- Update tool descriptions to list all five item_types and seven columns. Update any Literal/enum validation on the client side. Files the agent should NOT touch: - Server configuration, authentication, or non-sprint tools. ### Acceptance Criteria - [ ] `add_sprint_item` tool description lists `repo` and `project` as valid item_types - [ ] `get_sprint_board` tool description lists `repo` and `project` as valid item_types - [ ] `move_sprint_item` tool description lists `needs_approval` as a valid column - [ ] `add_sprint_item` tool description lists `needs_approval` as a valid column - [ ] Any client-side validation accepts the new values ### Test Expectations - [ ] Verify tool descriptions include new values (manual or automated) - Run command: `pytest` or manual MCP tool invocation test ### Constraints - Depends on pal-e-docs #66 landing first (API must accept new values before MCP sends them) - Match existing tool description patterns ### Checklist - [ ] PR opened - [ ] Tests pass - [ ] No unrelated changes ### Related - `project-pal-e-sprints` -- project this affects - pal-e-docs #66 -- API-side changes (dependency)