What
On gateway_attempts_read and gateway_issues_read, every allowed-value list has array appended:
gateway_attempts_read {"action":"list","dir":"sideways"} -> dir must be one of [asc, desc, array]
gateway_attempts_read {"action":"list","dir":"array"} -> dir must be one of [asc, desc, array]
gateway_issues_read {"action":"list","type":"bogus"} -> type must be one of [delivery, transformation, backpressure, request, array]
The message tells an agent to retry with a value that is then rejected.
gateway_events_read and gateway_requests_read produce correct lists, so it is specific to these routes.
Probably not ours
Grepping the CLI finds no enum validator producing this bracketed format, and pkg/gateway/mcp/tools.go already documents the API rejecting with must be one of [number, object, array] for a different field — so this looks like an API message passing through rather than something the CLI generates.
Worth confirming against the API before changing anything here. If it is server-side it needs raising with the API team; if the CLI is reshaping the message, it should stop appending the schema type to the value list.
Found during manual QA of v3.0.0.
What
On
gateway_attempts_readandgateway_issues_read, every allowed-value list hasarrayappended:The message tells an agent to retry with a value that is then rejected.
gateway_events_readandgateway_requests_readproduce correct lists, so it is specific to these routes.Probably not ours
Grepping the CLI finds no enum validator producing this bracketed format, and
pkg/gateway/mcp/tools.goalready documents the API rejecting withmust be one of [number, object, array]for a different field — so this looks like an API message passing through rather than something the CLI generates.Worth confirming against the API before changing anything here. If it is server-side it needs raising with the API team; if the CLI is reshaping the message, it should stop appending the schema type to the value list.
Found during manual QA of v3.0.0.