[ 
https://issues.apache.org/jira/browse/CAMEL-26963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18144959#comment-18144959
 ] 

Claus Ibsen commented on CAMEL-26963:
-------------------------------------

Thanks Federico. *Please remove {{camel_error_diagnose}}*, from both servers 
({{camel mcp}} and {{camel tui --mcp}}). It is not used, and we have too many 
MCP tools already.

The local-model stepwise benchmark (traces of Sep 20 to Nov 14 2026, almost all 
qwen3.6 35B-A3B on Ollama):

|| || Runs ||
| example runs | 7,305 |
| {{camel_error_diagnose}} offered | 7,225 |
| {{camel_error_diagnose}} called | 24 (0.3%) |
| ... of which a known exception was named | 4 |
| ... of which a recovery traces back to the answer | 0 |
| {{camel_get_errors}} called | 1,584 (3,028 calls) |
| a write whose reload answer reported the failure | 512 (762 answers) |

The AI panel of the Q&A benchmark (1,590 answers) never called it. The one 
specific diagnosis (BadSqlGrammarException) pointed to the Caused by line of 
the log, and that step still failed. The error already reaches the model 
through the reload answer of the write, {{camel_get_errors}} and the log.

What to remove: the tool in {{AuthoringTools}} and {{DiagnoseTools}}, 
{{ErrorDiagnoser}}, and the diagnose case of 
{{SourceValidatorResourceLiteralTest}}. The validator hint of CAMEL-24882 
stays. List it in the upgrade-guide entry with the other removed tools. Your PR 
or a follow-up, as you prefer.

_Claude Code on behalf of davsclaus_

> camel-jbang-mcp - remove or fold the niche and stale tools that the 
> consolidation does not cover yet
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-26963
>                 URL: https://issues.apache.org/jira/browse/CAMEL-26963
>             Project: Camel
>          Issue Type: Sub-task
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Assignee: Federico Mariani
>            Priority: Major
>             Fix For: 4.25.0
>
>
> This adds to the consolidation of the parent issue: tools it does not cover 
> yet, which are niche, stale or out of favor. Every tool is listed to every 
> client (CAMEL-25537), and in the evaluation of CAMEL-25537 (4.22.1, 1,729 
> calls) none of these tools was called.
> h3. Remove
> || Tool || Why ||
> | {{camel_ai_pipeline_scaffold}} | A template for one stack: Docling or 
> Textract, then Bedrock. The route it returns refers to beans it never defines 
> ({{#buildSummarizationPrompt}}, {{#buildRagPrompt}}, 
> {{#mergeDoclingAndTextract}}, {{#bedrockEmbedding}} and others), so it does 
> not run as its description says. Its default model is Claude Sonnet 4 
> ({{anthropic.claude-sonnet-4-20250514-v1:0}}), retired on the Claude API on 
> Jun 15 2026 (Amazon Bedrock sets its own dates), and its examples name Claude 
> Opus 4, also retired. An agent can build such a route with the catalog tools. 
> |
> | {{camel_route_cost_estimate}} | Prices written into the code, and prices 
> change faster than Camel releases. The parent issue found that it prices 
> Bedrock as Claude Sonnet whatever the model. |
> h3. Replace or remove
> || Tool || Why ||
> | {{camel_route_test_scaffold}} | It writes a JUnit 5 test in Java 
> ({{CamelTestSupport}} or {{@CamelSpringBootTest}}), and the parent issue 
> found that it tests a new route, not the real one. The tests that the CLI 
> runs are Citrus tests in YAML ({{camel test run}}), as the examples use them. 
> A scaffold of a Citrus YAML test for a given route would fit; otherwise drop 
> the tool. |
> h3. Fold or drop
> || Tool || Into || Why ||
> | {{camel_dependency_security_audit}} | {{camel_dependency_check}} | Both 
> read the POM. The audit matches the dependencies against the same advisory 
> data that {{camel_security_advisories}} returns. |
> | {{camel_error_diagnose}} | drop, unless a benchmark shows that it helps | A 
> fixed list of 19 exceptions with fixed causes. {{camel_get_errors}} returns 
> the real error of a running integration, and the catalog tools answer the 
> rest. |
> Keep {{camel_security_advisories}}: it returns the published CVE data, which 
> an agent cannot get otherwise. With the parent issue folding 
> {{camel_route_harden_context}} into {{camel_security_scan}}, two security 
> tools remain: the advisories and the scan.
> cc [~acosentino]: most of these tools came with CAMEL-23979 and CAMEL-24219 
> to CAMEL-24223, for 4.22.0. Please say if one of them has users we do not 
> know about.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to