retry-admissibility
Decide whether a failed HTTP call may be retried, must be reconciled, or must not be repeated — Given a request's method, how it ended (response status, timeout, reset, refused), idempotency-key evidence and optional caller policy, returns retry / do-not-retry / reconcile / unknown for an agent deciding what to do after a failed tool or API call. Encodes RFC 9110 method idempotency, the proxy and retry-of-a-retry rules and Retry-After parsing; a timeout or reset is never read as success or a
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>",
"ended": "<ended>"
},
"name": "retry-admissibility"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| asOf | No | RFC 3339 instant; needed only to turn a Retry-After HTTP-date into seconds. | |
| actor | No | ||
| ended | Yes | How the attempt ended. | |
| method | Yes | HTTP method, case-sensitive (GET, POST, ...). | |
| policy | No | ||
| status | No | Required when ended is 'response'. | |
| attempt | No | 1-based number of the attempt that just ended. Default 1. | |
| automatic | No | True when the retry would be issued automatically (library or proxy) rather than by a deliberate decision. | |
| retryAfter | No | Retry-After header value. | |
| requestSent | No | Whether request bytes reached the network. connection-refused and dns-failure imply not-sent. | |
| idempotencyKey | No | Caller-asserted evidence: the engine knows no vendor's key semantics. | |
| previousAttemptWasAutomaticRetry | No |