PiliLily opened a new issue, #513: URL: https://github.com/apache/rocketmq-dashboard/issues/513
## Background RIP-3 needs a stable, machine-readable contract before RocketMQ operations can be exposed consistently through CLI, MCP, and Studio UI clients. A previous all-in-one implementation was too large to review, so this issue deliberately tracks the first independently reviewable server-side slice. Competition context: https://www.taiyi.top/competition-details?id=2f410866-6fa3-11f1-b193-02420a000011 ## Proposed scope - Add a versioned YAML tool catalog and JSON Schema. - Validate the catalog, embedded input/output schemas, compatibility metadata, and exact handler registration at application startup. - Add capability-aware discovery backed by existing Studio cluster services. - Implement two read-only L1 tools: - `rmq.cluster.list` - `rmq.capabilities` - Preserve the existing `GET /api/ai/tools` response body while adding catalog metadata headers and additive tool metadata. - Add `POST /api/ai/tools/{name}/execute` with schema-validated input and output. - Keep cluster projection intentionally minimal: id, name, type, status, and version. ## Non-goals - No broker or NameServer access outside existing Studio services. - No write/destructive L2 or L3 tools. - No approval-token flow, MCP transport, Go CLI, or UI changes in this slice. Those pieces will be submitted as separate follow-up issues and small PRs so each change can be reviewed and merged independently. ## Compatibility and safety - Catalog version and minimum client version start at `1.0.0`. - The existing `Result<List<AiToolVO>>` response shape remains intact. - Only L1 handlers can execute. - Invalid catalogs, schemas, outputs, or handler mappings fail closed. - Unknown tools return a consistent 404 envelope. ## Validation - Full Maven build and test suite. - Spring application-context smoke test. - Packaged-JAR startup and live API smoke tests. - Existing frontend lint/build and AI API tests. -- 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]
