stability: validate enum-style string parameters (sort/order/state) #10
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Several tools accept open string parameters that the Gitea API only honors for a fixed enum (
sort,order,state,type, etc.) — e.g.operation/search/search.goforSearchReposTool. Invalid values are passed through verbatim; Gitea silently ignores them, producing surprising results without any error surfaced to the MCP client.Suggested direction
mcp.Enum(...)in the tool schema where the value set is known