The Wire · Showcase
SPRING AI TOOLS API OVERHAUL SHIPS WITH AUTO-REGISTRATION AND FLUENT DSL
By RepoJournal · Filed · About Spring
Spring AI replaced its scattered tool-registration methods with a unified ToolSpec fluent API while automatically wiring ToolCallAdvisor when tools are configured.
The AI team landed three major capability upgrades overnight. ToolCallAdvisor now auto-registers when tools are configured on ChatClient [1], eliminating boilerplate setup and automatically tuning stream behavior based on whether you call() or stream(). The new ToolSpec fluent API [2] consolidates what were scattered toolCallbacks, toolNames, and toolContext overloads into a single consumer-based entry point with instances(), callbacks(), context(), and advisor() methods, deprecating the old overloads for cleaner code. BeanOutputConverter was refactored to reuse the core JsonSchemaGenerator [3], removing postProcessSchema() as an extension point and recursively applying additionalProperties: false to nested schemas for better schema safety. Spring cleaned up the integration-tests bindings config for main [8], while also removing unused HanaDB properties [6] and CosmosDB components entirely [7] with upgrade docs shipped alongside. Spring Security bumped JUnit to 6.1.0 [9] and CAS client to 4.1.1 [10] with no breaking changes. Spring Integration added DSL support for Redis Stream Channel Adapters [4] [5], a long-requested feature for reactive stream patterns.
Action items
- → Review ToolSpec migration if you use ChatClient tool registration - old methods are deprecated spring-projects/spring-ai [plan]
- → If using CosmosDB or HanaDB in Spring AI, check upgrade notes and plan extraction to external modules spring-projects/spring-ai [plan]
- → Upgrade Spring Security dependencies to pick up JUnit 6.1.0 and CAS 4.1.1 in your next build spring-projects/spring-security [monitor]
- → Test Spring Integration Redis Stream adapters if you're on the DSL path spring-projects/spring-integration [monitor]
References
- [1] feat(ChatClient): Auto-register ToolCallAdvisor when tools are configured spring-projects/spring-ai
- [2] feat(ChatClient): introduce ToolSpec fluent API spring-projects/spring-ai
- [3] GH-5884: Reuse JsonSchemaGenerator in BeanOutputConverter spring-projects/spring-ai
- [4] GH-8108: Add DSL for Redis Stream Channel Adapters ↗ spring-projects/spring-integration
- [5] GH-8108: Add DSL for Redis Stream Channel Adapters spring-projects/spring-integration
- [6] Remove unused Hanadb properties and other configs spring-projects/spring-ai
- [7] Remove CosmosDB related components from Spring AI spring-projects/spring-ai
- [8] Fix spring-cloud-bindings for main branch spring-projects/spring-ai-integration-tests
- [9] Bump org.junit:junit-bom from 6.0.3 to 6.1.0 ↗ spring-projects/spring-security
- [10] Bump org.apereo.cas.client:cas-client-core from 4.1.0 to 4.1.1 ↗ spring-projects/spring-security
FAQ
- What changed in Spring on May 21, 2026?
- Spring AI replaced its scattered tool-registration methods with a unified ToolSpec fluent API while automatically wiring ToolCallAdvisor when tools are configured.
- What should Spring teams do about it?
- Review ToolSpec migration if you use ChatClient tool registration - old methods are deprecated • If using CosmosDB or HanaDB in Spring AI, check upgrade notes and plan extraction to external modules • Upgrade Spring Security dependencies to pick up JUnit 6.1.0 and CAS 4.1.1 in your next build
- Which Spring repositories shipped on May 21, 2026?
- spring-projects/spring-ai, spring-projects/spring-integration, spring-projects/spring-ai-integration-tests, spring-projects/spring-security