Croway commented on PR #29047: URL: https://github.com/apache/camel/pull/29047#issuecomment-6606757476
Thanks for this. The chaos tools are well gated: chaos must already be on in the application, rules never change over HTTP, and `add`/`change` are confirmed first. The issue is where they go. We do not want to fill the context of `camel-jbang-mcp` more than needed, so only tools that are strictly needed should go there. Today every `@Tool` of `camel-jbang-mcp` is in `tools/list` for every client. The only `ToolFilter` is `McpAccessFilter`, and it returns `true` for every tool unless `camel.mcp.security.enabled=true`. The `chaos` tool group does not change this: only clients that call `camel_runtime_tool_groups` (`camel ask`, the TUI, clients for small models) use it. Claude Code, Cursor and similar clients load every tool at startup. This PR adds six tools to the prompt of every session, also when the integration has no `camel-chaos`, for a feature that is dev-only and opt-in. The server has about 85 tools on `main` (about 17.6k tokens at startup when I measured it in October, with 86 tools), and CAMEL-25639 is meant to bring that number down, not up. Please put the MCP part of this PR on hold until CAMEL-25537 (tool profiles and an allow-list) lands. Chaos can then be a profile that is off by default, and only the users who turn it on pay for it. The atomic status write in `FileCliConnectorTransport` and the `AskTools` fix (longest names first) do not depend on the chaos tools. They could go in a separate PR in the meantime. _Claude Code on behalf of Croway_ -- 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]
