The per-tool pages under the MCP reference are generated from the server’s own tool manifest, and until now that manifest carried names only. It carries each tool’s parameter schema and a return description as well, so all 31 pages show what the tool needs, which of those parameters are required, and what comes back. The build still fails in either direction if the page set and the server registry disagree.
describe_connection got its own documented row, which the parity check
required.
Three error codes are explained on the API reference rather
than only appearing in a response: expired_read_only (402) when a workspace is
in the post-trial read-only landing, api_disabled (403) when live API is off
for the score that owns the model, and deploy_blocked (409) when the org’s
deploy policy is set to block and the model’s validation state is not passed.
One correction: the webhook endpoint’s 400 was described as firing on more than 1000 records in a batch, on an endpoint that takes one record. The description is fixed at its source, which is the published OpenAPI document the page renders verbatim.