feat(examples): add sports RPC example with ESPN API tool calls

[robinandeer]

Add a sports assistant RPC example that calls the ESPN public API — same endpoints a client reported 10s freezes on when used with tool calling.

What it demonstrates:

• 4 backend RPC tools (get_scores, get_standings, get_news, get_leaders) making real HTTP requests to ESPN
• Instrumented timed() wrapper on each tool handler that logs: when the call arrives, args, execution time, and response size returned to the model
• Helps isolate whether latency is server-side (API call) or model-side (processing/speaking delay)

What we found testing it:

• ESPN API calls complete in ~130-160ms
• Full server-side tool execution is ~157ms
• The reported freeze is model-side, not API-side

[rpc #1] ▶ get_standings called — args: {"league":"NBA"}
[espn] Fetching: .../basketball/nba/standings
[espn] Done in 157ms
[rpc #1] ◀ get_standings done — 157ms (613 bytes returned to model)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
avatars-playground	Ready	Preview, Comment	Apr 8, 2026 10:01pm

[robinandeer]

• feat(examples): add sports RPC example with ESPN API tool calls #14 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.