HTTP Status Code Lookup
ref_http_statusLook up an HTTP status code by number or keyword. Returns the reason phrase, description, category (1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error, 5xx Server Error), whether the code is cacheable by default, and the defining RFC with section reference. For keyword queries, returns the closest match plus alternatives.
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": {
"query": "<query>"
},
"name": "ref_http_status"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Numeric status code (e.g., "404" or "422") or descriptive keyword (e.g., "not found", "too many requests", "unprocessable"). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| rfc | No | Defining RFC (e.g., "RFC 9110"). | |
| code | No | HTTP status code number. | |
| error | No | Present when the call failed. Absent on success. | |
| category | No | Status code category (1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error, 5xx Server Error). | |
| cacheable | No | Whether this status code is cacheable by default per RFC 9110. | |
| description | No | Human-readable description of when and why this status is used. | |
| rfc_section | No | RFC section number (e.g., "15.5.5"), or null if not applicable. | |
| alternatives | No | Other status codes that matched the keyword query. Present only for keyword searches with multiple matches. | |
| reason_phrase | No | IANA reason phrase (e.g., "Not Found"). |