[
https://issues.apache.org/jira/browse/CAMEL-24897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-24897.
---------------------------------
Resolution: Fixed
> camel-jbang-mcp - camel_write_file: drop the validate flag, an agent turns it
> off
> ---------------------------------------------------------------------------------
>
> Key: CAMEL-24897
> URL: https://issues.apache.org/jira/browse/CAMEL-24897
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 4.23.0
>
>
> The camel_write_file tool (camel-jbang-mcp server and the camel-jbang views)
> has a boolean {{validate}} argument, default true, and its refusal message
> ends with "(validate=false writes it anyway)". In the camel-jbang-mcp
> stepwise benchmark the local model sets {{validate: false}} on its own: 9 of
> 26 writes in series s6 (the HTTP rungs, thinking off), 26 of 337 in s3, often
> on the first write of a step with no refusal to provoke it. The invalid file
> then reloads, the app runs without routes (a single route file has nothing to
> restore, CAMEL-24860), and the model reads the validator's report from the
> log (CAMEL-24851) instead of getting it from the write.
> The flag exists for a person who knows better; for an agent it is a bypass of
> the one deterministic check we have. Remove the argument from the tool (the
> write validates, always) and the sentence from the refusal message. A person
> who wants to write an invalid file has the editor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
