Lucio Lelii
effb506572
The planning and block-config models never saw which MCP servers were declared, so they could not reach for tool-running steps (writing to a workspace, compiling, running shell) - the coding-agent-mcp server was effectively invisible and the assistant fell back to HTTPServerCall. - Inject the declared MCP catalog (id/name/description) into both the PLAN and BLOCK_CONFIG prompts, and steer MCPAgent/MCPAgentChat toward running declared-server tools instead of emulating them via HTTP. - Let the model bind a concrete catalog server via mcpServers; validate chosen serverName against the catalog and drop hallucinated ids so a bad choice degrades to a clean validation/fallback path instead of a runtime "Unknown MCP server" failure. The model's explicit choice is preserved and no longer overwritten by the rag default. Tests: catalog reaches both prompts; a chosen catalog server is kept; an unknown server id is dropped. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .mvn/wrapper | ||
| src | ||
| .gitattributes | ||
| .gitignore | ||
| Dockerfile | ||
| mvnw | ||
| mvnw.cmd | ||
| ollama-preloaded-docker | ||
| pom.xml | ||