http-outcome
Classify an HTTP response as success, retry, reconcile or stop, with the wait it asks for — Classifies one HTTP response (method, status, headers) as success / retry / reconcile / stop for an agent that just called an API, and reads the wait from Retry-After (RFC 9110: delay-seconds or any of the three HTTP-date formats) or from a vendor delay header whose dialect the caller declares (seconds, milliseconds, epoch seconds, epoch milliseconds, HTTP-date). Caller-supplied vendor rules (stat
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"method": "<method>",
"status": "<status>"
},
"name": "http-outcome"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| asOf | No | RFC 3339 instant; needed to turn an HTTP-date or epoch delay into seconds. | |
| method | Yes | ||
| status | Yes | ||
| headers | No | Response headers as name/value pairs (names compared case-insensitively). | |
| delayHeader | No | Which header carries the wait and in what dialect. Default is Retry-After under RFC 9110. | |
| vendorRules | No | First matching rule wins. | |
| idempotencyKey | No |