Load and fully dereference an OpenAPI/Swagger spec from a URL or local file path (JSON or YAML). Call this first. Returns the API title, servers, and every documented endpoint.

List every endpoint (method + path) from the currently loaded API spec.

Make an actual HTTP call to a documented endpoint and return the real status, headers, and body. Does not validate the response — use test_endpoint if you also want schema validation.

Check a response body against the JSON schema documented for a given method + path + status code.

Call a documented endpoint with real parameters, then validate the real response against its documented schema. Returns pass/fail plus the specific mismatches found. This is the main tool for 'does this endpoint actually work as documented'.

Best-effort run across every GET endpoint that needs no required parameters: calls each one for real and validates the response against the documented schema. Endpoints needing parameters are listed as skipped (use test_endpoint for those individually), and DELETE/OPTIONS/HEAD are never auto-run. Set includeMutating: true to also auto-generate example params/bodies from the schema and attempt POST/PUT/PATCH endpoints — off by default because that can create or modify real data on the live API.

One-shot health check: calls each given endpoint (or, if none given, every parameter-free GET in the loaded spec) and reports whether it responded, its status code, and latency. Useful for a quick 'is the API up' pass, e.g. before a demo or as part of CI.

Compare two OpenAPI/Swagger specs (each a URL or local file path — e.g. an old tag vs. the current main) and report added/removed endpoints plus request/response schema changes, flagging which ones are likely to break existing clients (removed fields, newly-required fields, type changes, removed enum values) versus safe additive changes. Does not affect the spec currently loaded for the other tools.