Check one supplied OpenAPI 3.1 inline response against status, explicit JSON media type, parsed JSON body and deserialized headers. Exact status precedes class and default; unsupported references and schemas are explicit. Not full OpenAPI validation, wire decoding, authentication or request execution.
Choose for: Validate supplied API response body and response headers against OpenAPI Select exact status, response class or default before checking JSON output
Outside this profile: Full OpenAPI conformance, reference resolution, parameter serialization, wire parsing or live API tests Proving absence of body is an error solely because content is documented
Inspect a supplied MCP CallToolResult text/structured-content envelope and optional object-root output schema. Separates tool execution errors, missing structured output, invalid text blocks and unsupported content/schema features. Does not invoke tools or prove MCP interoperability, provenance, or trust.
Choose for: Validate MCP tool result structuredContent against outputSchema Distinguish tool execution error from malformed tool result envelope
Outside this profile: MCP lifecycle, JSON-RPC correlation, binary/media/resources, annotation validation or security verdicts Full JSON Schema or trusting tool output because its shape passes
Parse a completed, already-decoded server-sent-event text snapshot into dispatched events, committed last-event ID, exact decimal retry milliseconds and ignored-field count. Handles CR/LF/CRLF, one leading BOM, blank dispatch and incomplete EOF discard. No live connection, resumption or provider-specific event semantics.
Choose for: Parse saved SSE event stream and inspect last event ID Diagnose missing events caused by incomplete final blank line
Outside this profile: Opening an SSE stream, joining arbitrary incremental chunks or retrying connections Raw-byte UTF-8 decoding, provider completion markers or JSON-RPC protocol validation
Inspect supplied newline-delimited JSON text into parsed records with line numbers and exact UTF-16 spans, bounded per-line diagnostics, explicit empty-line policy and optional final-newline requirement. Rejects bare CR, unsafe keys, nonfinite numbers and excessive structure; no lossless number or duplicate-key preservation.
Choose for: Validate JSON Lines or NDJSON batch artifacts with exact failing line numbers Parse newline JSON tool logs while keeping source offsets and malformed-line diagnostics
Outside this profile: Streaming network ingestion, arbitrary log formats or multiline JSON documents Lossless large numbers, duplicate-key detection or implicit repair
Expand RFC6570 scalar string variables with simple, reserved, fragment, label, path, path-parameter and query operators. Explicitly rejects prefix/explode modifiers, lists/maps and non-ASCII variable names/literals. Missing/null variables are omitted with an audit list; no URL fetch, safety verdict or encoding guesswork.
Choose for: Expand scalar RFC6570 API URL templates without accidental slash or query injection Construct path and query expressions with explicit reserved expansion
Outside this profile: Full RFC6570 level 4, prefix/explode/list/map expansions or arbitrary Unicode template literals URL authorization, host allowlisting, SSRF safety or fetching
Inspect one structured CloudEvents 1.0 JSON artifact for required attributes, string restrictions, time/calendar profile, data/data_base64 conflicts, canonical Base64 and primary extension mappings. URI checks are ASCII lexical only. No webhook signatures, transport binding, extension semantics or event authenticity checks.
Choose for: Validate a supplied CloudEvents structured webhook envelope before ingestion Detect conflicting CloudEvents payload modes and invalid extension attributes
Outside this profile: Authenticating webhook senders, binary HTTP bindings, schema fetching or complete URI conformance Leap-second validation or secondary structured extension mappings
Parse supplied HTTP Link field values with quote-aware commas, escaped quoted parameters, relations and anchor context. Preserves raw URI references/parameters and first-rel semantics; flags unsupported extended parameters. Does not resolve/fetch links, apply anchors, inspect live pagination or certify full RFC8288 conformance.
Choose for: Extract pagination next and last relations from supplied HTTP Link headers Parse quoted comma parameters and detect anchor-dependent links
Outside this profile: Following pagination links, URL resolution, link safety or decoding extended title parameters Treating an anchored link as if it belonged to the original response context
Evaluate supplied If-Match and If-None-Match against caller-asserted representation existence/current ETag, preserving strong/weak comparison and precondition order. Gives conditional 304/412 or proceed guidance only. Excludes date/range/freshness, duplicate-write exceptions, permission decisions and live requests.
Choose for: Evaluate conditional HTTP ETag cache validation and optimistic concurrency preconditions Distinguish weak If-None-Match from strong If-Match and wildcard existence
Outside this profile: Cache freshness, date validators, HTTP ranges, fetching resources or deciding replay authorization Guaranteed success status or inferring current representation from an ETag alone
Compose inert ASCII RFC 9421 request signature-base and Signature-Input artifacts from ordered, supplied non-secret field examples and explicit context. Does not sign, verify, authorize or send requests.
Choose for: Build an inert signature-base example from supplied request context and ordered ASCII field lines Compare raw and binary-wrapped field boundaries before using an external signer
Outside this profile: Signing, verification, keys, credentials, authentication, authorization, payment, or live HTTP requests Responses, trailers, CONNECT, query-parameter selection, Structured Field parsing, Unicode or obs-text fields Secret or production request payloads, including secrets in targets, free text or key identifiers
Resolve a strict supplied HTTP bytes Range field against an exact decimal representation length, retaining requested order, duplicates, unsatisfied members and half-open spans. No coalescing, server preconditions, fetching or response transmission.
Choose for: Inspect bounded Range syntax and exact byte spans even when only a large representation length is available
Outside this profile: No remote fetching, request transmission, filesystem access, caching, content decoding or authenticity verification No server policy, method, conditional request or If-Range enforcement; callers must check applicability separately Not a full HTTP parser: unsupported units, empty list members, inner whitespace and numbers over 20 digits are rejected by this bounded profile
Compose exact inert single-range or multipart/byteranges 206 bodies, or an empty 416 artifact, from supplied nonempty Base64 bytes and a strict Range field. Byte-preserving order, offsets, fields and SHA-256; no conditional-request checks or transmission.
Choose for: Create bounded partial-content test artifacts from inline bytes without decoding or contacting a server
Outside this profile: No remote fetching, request transmission, filesystem access, caching, content decoding or authenticity verification No server policy, method, conditional request or If-Range enforcement; callers must check applicability separately Not a full HTTP parser: unsupported units, empty list members, inner whitespace and numbers over 20 digits are rejected by this bounded profile Empty representations, media-type parameters, automatic boundary generation or boundary tokens appearing anywhere in selected payloads