CTS / example

error-envelope.json

Inspect a structured JSON error response.

DownloadView source file Read related standard

Useful when

My CLI interface is inconsistent.

Choose your situation

What you should change

Replace error codes, messages and context with your command contract.

Use only the parts that help. These are starting points, not rigid requirements.

View resource

{
  "status": "error",
  "tool": "example-command",
  "version": "1.0.0",
  "data": null,
  "warnings": [],
  "errors": [
    {
      "code": "input-missing",
      "message": "Required input path was not found.",
      "path": "input.txt"
    }
  ]
}