@McpToolbox defined tool not available when AiService is constructed manually

[bitsofinfo]

Hi,
I am manually constructing an AiService like this:

Class<? extends InferenceService> inferenceServiceClass = MyTools.class;

InferenceService service = AiServices.builder(inferenceServiceClass)
      .systemMessageProvider(memoryId -> systemPromptDef.renderPrompt())
      .chatModel(aiModel.getChatModel())
      .chatMemoryProvider(config.getChatMemoryProvider())
      .hallucinatedToolNameStrategy((req ->
              new ToolExecutionResultMessage(req.id(),req.name(),
                      "[Tool output omitted due to hallucination]")))
      .build();

the inferenceServiceClass is = MyService.class:

public interface InferenceService {
    String invoke(String message, String memoryId);
}

@CreatedAware
public interface MyService extends InferenceService {

    @ToolBox({
            WebSearchTool.class,
            MessageRecordTool.class
    })
    @McpToolBox("mytools") 
    @Override
    String invoke(@UserMessage String message, @MemoryId String memoryId); 

}

The mcp tool defined as mytools is properly setup in application.yaml. However this tool is never available. I don't see it being sent in the list of tools to the llm. (the others (websearch/message record) are being sent OK.

I also had to put this @CreatedAware on the interface and I'm not sure why.

thanks!

[geoand]

Generally, manually constructed AI Services are hit and miss with Quarkus LangChain4j

[jmartisk]

Yeah I think we will need to figure out how to plug Quarkus-specific stuff (@McpToolBox) in this case. Basically, it's only taken into account for declaratively created AI services that are initialized at build time..

Until then, I guess you'll need to either use CDI to inject the AI service, or if you really can't go declarative, then work around this by passing a tool provider to the AiServices builder instead.