Check the public URL
deployments_checkRequest this deployment over its public URL and report what came back. Use it after deploying or fixing a site to confirm it really works - "the logs say it started" is not the same as "the page loads". Returns the HTTP status and the start of the body, so a 500 or a stack trace is visible. Server-rendered output only: no JavaScript runs. Any method: POST a JSON body to test an API route. On a 2xx HTML page it also requests the first same-origin links and assets it finds (links) and names the broken ones and duplicated nav entries in note. It goes through the public URL, the way a visitor does. To hit many routes at once or load-test, one deployments.shell command with a curl loop on localhost:$SERVER_PORT is cheaper than one check per URL. To ask what is wrong with a deployment rather than what one URL returns, call deployments.diagnose instead: it answers this plus the state, the logs and the startup config in one call.
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": {
"id": "<id>"
},
"name": "deployments_check"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| body | No | Request body. An object is sent as JSON (Content-Type set for you); a string is sent as is. | |
| path | No | Path to request, e.g. '/' or '/api/scores'. Defaults to '/'. | |
| method | No | Default GET. | |
| headers | No | Extra request headers, e.g. Authorization. |