RockteMQ-AI commented on issue #4646: URL: https://github.com/apache/rocketmq-dashboard/issues/4646#issuecomment-5754861227
**Issue Evaluation** Category: `bug` | Status: **Confirmed** | Severity: **Medium** The reported issue has been verified. The MCP message query tools (`rmq.message.query_by_topic` and `rmq.message.query` key path) silently truncate results at the 200-message limit (`MessageService.TOPIC_QUERY_RESULT_LIMIT`) without signaling truncation to the caller. **Root Cause:** No truncation indicator in the tool output. Callers (LLM agents via MCP, `rmqctl` via CLI) cannot distinguish "no more matching messages" from "budget reached". **Impact:** Misleading query results — a busy topic queried with a broad tag returns the first 200 rows and appears exhaustive. Callers may incorrectly conclude the topic has no more matching messages. **Resolution:** PR #4645 correctly adds a `truncated: true` signal when the result budget is reached. --- *Automated evaluation by RockteMQ-AI* -- 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]
