[
https://issues.apache.org/jira/browse/CAMEL-23477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-23477.
--------------------------------------
Resolution: Fixed
> camel-jbang-mcp: stop re-embedding pomContent inside migrateProject prompt
> --------------------------------------------------------------------------
>
> Key: CAMEL-23477
> URL: https://issues.apache.org/jira/browse/CAMEL-23477
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Affects Versions: 4.21.0
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.21.0
>
>
> h3. Context
> Part of an effort to reduce token consumption of the {{camel-jbang-mcp}} MCP
> server. The module exposes 31 tools, 6 resources, and 3 prompts; both tool
> schemas (loaded once per session) and tool results (per call) contribute to
> LLM context-window pressure for every user of the server.
> Related tickets in this effort are linked via "Relates to".
> {{PromptDefinitions.migrateProject}} ({{PromptDefinitions.java:103}}) takes a
> {{pomContent}} arg and inlines the full pom inside the workflow instructions
> at {{PromptDefinitions.java:119}}. The client typically already has the pom
> in its conversation context, so embedding it inside a multi-paragraph
> instruction block duplicates content.
> The workflow text itself (Step 1 … Step N) is also verbose for what could be
> a 5-line numbered list.
> h3. Proposed change
> * Reference "the pom.xml you already have" rather than inlining {{%s}} with
> the full content, OR make the pom inline optional.
> * Compress the workflow descriptions.
> h3. Acceptance
> Prompt size does not scale with {{pomContent}} length.
> ----
> _Filed by Claude Code on behalf of Andrea Cosentino_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
