davsclaus opened a new pull request, #26668: URL: https://github.com/apache/camel/pull/26668
Fixes https://issues.apache.org/jira/browse/CAMEL-24867 The MCP server wraps the shared runtime tool registry in `RuntimeTools`, but only 27 of its runtime tools. A model working through the MCP server on an app with a datasource could not look at the database at all, nor at circuit breakers, metrics, spans, EIP statistics, startup steps, route analysis or configuration drift, although the running app answers all of them and the camel-jbang views and the agent REPL already have them. This adds ten wrappers with the same `camel_runtime_*` naming and delegation as the existing ones: | Tool | Registry tool | |---|---| | `camel_runtime_sql` | `execute_sql` | | `camel_runtime_datasources` | `get_datasources` | | `camel_runtime_sql_trace` | `get_sql_trace` | | `camel_runtime_circuit_breakers` | `get_circuit_breakers` | | `camel_runtime_metrics` | `get_metrics` | | `camel_runtime_eip_stats` | `get_eip_stats` | | `camel_runtime_spans` | `get_spans` | | `camel_runtime_startup_steps` | `get_startup_steps` | | `camel_runtime_route_analysis` | `get_route_analysis` | | `camel_runtime_config_drift` | `detect_config_drift` | The remaining unwrapped registry tools are covered by other MCP tools already (catalog, examples, errors, eval, control, heap dump, processes). Documented in a new "Data, Resilience and Analysis" table of the camel-jbang-mcp page. Tests: `RuntimeToolsTest` checks the required argument of the sql tool and that every wrapper names a registry tool that exists. Found while preparing the CAMEL-24834 tool-group experiment on the camel-jbang-mcp server: the sql example on H2 was meant to compare the authoring set with and without the sql tools, and the server had none of them. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01Bp3538HRBPMQkb5ta9xRaj -- 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]
