[FEATURE] Tools and Agents event emit for websocket #1133
Description
Problem Statement
Front-end applications need predictable component discovery patterns for dynamic UI generation and type safety. UI developers spend excessive time parsing streaming responses and handling contract changes, leading to brittle integrations
Proposed Solution
StrandsAgents should emit named tools and agents as ready-to-use components for front-end integration when they're initialized, not as part of the streaming response. This would eliminate the current approach where front-ends must constantly parse tool responses and match them with tool usage events, which is fragile when contracts change.
Use Case
StrandsAgents should emit named tools and agents as ready-to-use components for front-end integration when they're initialized, not as part of the streaming response. This would eliminate the current approach where front-ends must constantly parse tool responses and match them with tool usage events, which is fragile when contracts change.
Alternatives Solutions
No response
Additional Context
No response