iloveeyjafjalla opened a new issue, #6866:
URL: https://github.com/apache/rocketmq-dashboard/issues/6866
## Summary
`rmqctl message query-dlq` (MCP tool `rmq.message.query_dlq`) has two modes
and silently drops the input that cannot apply to the selected one — and,
without a start time, silently narrows its answer to the **last hour**:
- `--search` is read only by the group listing: with `--group-name`,
`MessageQueryDlqToolHandler.execute` calls `listGroups(…, input.search(), …)`
in the other branch only.
- `--start-time` / `--end-time` are read only by the message listing:
without `--group-name`, the window is dropped the same way.
- Without `--start-time`, the message listing defaults to one hour:
`RocketMQDLQProvider.listMessages`
(`server/src/main/java/org/apache/rocketmq/studio/provider/apache/RocketMQDLQProvider.java:334-338`)
sets `end = endTime ?? now` and `begin = startTime ?? end - ONE_HOUR_MILLIS`.
None of that is discoverable from the tool. The four properties carry no
description, so the CLI renders them as bare names, and an MCP client — which
has no `--help` — receives only the schema:
```
$ rmqctl message query-dlq --help
--group-name string group name
--search string search
--start-time int start time
--end-time int end time
```
A caller therefore reads "the DLQ is empty" from a window it never chose,
and passes a search term that is dropped without a word. The sibling tool
documents exactly this kind of applicability ("The startTime/endTime window
only applies to the uniqueKey and key paths", `message.yaml:7`).
## Expected
The schema states which mode each filter belongs to, the unit it is
expressed in, and what an omitted window means — the same facts `--help`,
`explain` and every MCP client read from it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
