Schema validation for MCP content.
Experimental
Helper utilities outside the core Handler/DSL path. Prefer tool
output_schema on ExMCP.Server.DSL for structured tool results.
Field/size/MIME helpers are implemented. validate_schema/3 uses
ExJsonSchema behind ExMCP.Content.SchemaPolicy, which rejects remote
references and bounds schema complexity and execution time.
Summary
Functions
Preflights and resolves a JSON Schema under ExMCP's resource policy.
Validates content format and structure.
Validates content size against maximum limits.
Validates MIME types against allowed types.
Validates that required fields are present and non-empty.
Validates content against a JSON Schema using ExJsonSchema.
Types
@type validation_result() :: :ok | {:error, [validation_error()]}
Functions
@spec compile_schema( map() | boolean(), keyword() ) :: ExMCP.Content.SchemaPolicy.compile_result()
Preflights and resolves a JSON Schema under ExMCP's resource policy.
@spec validate_format(ExMCP.Content.Protocol.content()) :: validation_result()
Validates content format and structure.
@spec validate_max_size(ExMCP.Content.Protocol.content(), pos_integer()) :: validation_result()
Validates content size against maximum limits.
@spec validate_mime_types(ExMCP.Content.Protocol.content(), [String.t()]) :: validation_result()
Validates MIME types against allowed types.
@spec validate_required_fields(ExMCP.Content.Protocol.content()) :: validation_result()
Validates that required fields are present and non-empty.
@spec validate_schema( ExMCP.Content.Protocol.content() | map(), map() | boolean(), keyword() ) :: validation_result()
Validates content against a JSON Schema using ExJsonSchema.
Content maps are converted to JSON-compatible string-keyed maps (atoms become strings) before validation.