Diagnose a proxy error
diagnose_proxy_errorUse structured client/version, phase, status or exception observations to identify possible causes and the next check. Returns uncertainty and retry boundaries. Do not send raw logs, URLs or credentials.
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": {
"client": "<client>",
"version": "<version>",
"phase": "<phase>"
},
"name": "diagnose_proxy_error"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| phase | Yes | ||
| client | Yes | ||
| method | No | unknown | |
| status | No | Observed HTTP status; identify its responding layer separately. | |
| version | Yes | ||
| exception | No | Normalized category, not raw exception text. HTTPX ConnectError alone does not establish a TLS error. | |
| responseSource | No | Use target/proxy only when established by response provenance, not merely the status code. | unknown |
| retryAfterSeconds | No | Parsed bounded Retry-After delay, if actually observed. Never submit the raw header. | |
| requestMayHaveBeenSent | No | Whether this target request may already have reached the application. Omit when unknown. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| retry | Yes | ||
| client | Yes | ||
| sources | Yes | ||
| summary | Yes | ||
| version | Yes | ||
| evidence | Yes | ||
| candidates | Yes | ||
| uncertainty | Yes | ||
| rulesRevision | Yes |