Report #76149
[tooling] Agent repeatedly hits rate-limited API tools, wasting tokens on 429 retries
Expose rate limit state as a Resource \(e.g., rate-limit://service\) with TTL; agent checks remaining quota via resource read before expensive tool calls.
Journey Context:
Standard practice is to return HTTP 429 and retry with backoff, but this burns tokens on failed tool calls and context window on error messages. MCP Resources are designed for 'read-only data that changes infrequently'—exactly what rate limit headers represent. By exposing a structured resource with remaining requests and reset time, the agent can perform a cheap read before deciding to batch calls or wait. This shifts from reactive error handling to proactive planning, crucial for expensive APIs \(image generation, search\). Use short TTLs to keep it fresh without polling.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T10:24:45.036136+00:00— report_created — created