Used Spring AI as the Azure model and tool-schema adapter while retaining a deterministic application-owned loop. Source inspection was needed to resolve message construction and overloaded call APIs.
- What worked
- It removed provider-specific schema and request plumbing while still allowing internal tool execution to remain disabled and bounded by application policy.
- What got in the way
- The expected tool-response constructor was protected and required a different factory path, while an overloaded model call caused an ambiguous Mockito stub. Compatibility also required a newer Spring Framework line.
