Is your feature request related to a problem? Please describe.
When I create MCP Tools out of an OpenAPI spec, the intent routing does not go via URLs but via operation ids.
For conversational AI chatbots like adk I want to
- enrich the response with a hint for the chatbot to choose the next operationId
- test the intent routing based on expected operationIds
Describe the solution you'd like
I implement the api controllers within Spring Boot.
When I want to refer to a given operationId, I need to access the operationId via a constant value. Otherwise I cannot guarantee during compile time that intent routing or the operationIds in the response actually exist.
Describe alternatives you've considered
Currently I override the api.mustache template in my Java Spring project exposing the operationId as a constant similar the already existing PATH constant.
Additional context
Implementation done within Spring Boot.
Is your feature request related to a problem? Please describe.
When I create MCP Tools out of an OpenAPI spec, the intent routing does not go via URLs but via operation ids.
For conversational AI chatbots like adk I want to
Describe the solution you'd like
I implement the api controllers within Spring Boot.
When I want to refer to a given operationId, I need to access the operationId via a constant value. Otherwise I cannot guarantee during compile time that intent routing or the operationIds in the response actually exist.
Describe alternatives you've considered
Currently I override the api.mustache template in my Java Spring project exposing the operationId as a constant similar the already existing PATH constant.
Additional context
Implementation done within Spring Boot.