Loading server...
{
"type": "object",
"properties": {
"old_contract_json": {
"type": "string",
"description": "Must be valid JSON text representing the previous contract version. The tool must reject empty input and invalid JSON with a parse error."
},
"new_contract_json": {
"type": "string",
"description": "Must be valid JSON text representing the proposed contract version. The tool must reject empty input and invalid JSON with a parse error."
},
"strict_mode": {
"type": "boolean",
"description": "When true, treat type changes, removed required fields, removed paths, enum narrowing, and object-to-non-object changes as breaking. When false, still report them but additive changes may be separated more prominently."
},
"show_path_details": {
"type": "boolean",
"description": "When true, include full normalized JSON paths for every finding. When false, keep messages concise while preserving path references in structured results."
},
"ignore_additive_changes": {
"type": "boolean",
"description": "When true, do not include new optional fields, new array members in additive-only contexts, or other non-breaking additions in the visible change lists."
}
},
"required": [
"old_contract_json",
"new_contract_json",
"strict_mode",
"show_path_details",
"ignore_additive_changes"
],
"additionalProperties": false
}
API Pagination and Cursor Consistency Checker
api-pagination-and-cursor-consistency-checker
Backend and frontend teams need to confirm that paginated API response samples keep page, offset, and cursor behavior consistent across endpoints and edge cases.
Schema valid · SHA-256 ed514967a7fe…
View input schema
{
"type": "object",
"properties": {
"response_samples": {
"type": "string",
"description": "Must contain one or more API response samples in JSON text form. Each sample must parse as an object or array. Empty input is invalid."
},
"pagination_mode": {
"type": "string",
"enum": [
"cursor",
"page",
"offset",
"mixed"
],
"description": "Select the intended pagination contract. 'mixed' means samples may contain more than one pagination style and the checker will verify consistency within each style."
},
"sort_key": {
"type": "string",
"description": "Optional. If provided, must be a non-empty field path such as 'created_at' or 'data.items[].id'. Used as the expected stable ordering key across samples."
},
"page_size": {
"type": "number",
"minimum": 1,
"maximum": 1000000,
"description": "Optional. If provided, must be a positive integer. Used to verify per-page item counts and boundary transitions."
},
"show_item_paths": {
"type": "boolean",
"description": "When true, output item path references for duplicates, gaps, and boundary findings when they can be inferred from the samples."
}
},
"required": [
"response_samples",
"pagination_mode"
],
"additionalProperties": false
}
CSS Stacking Context and Paint Order Inspector
css-stacking-context-and-paint-order-inspector
UI developers need to know why an element is behind another element, clipped unexpectedly, or trapped inside a stacking context.
Schema valid · SHA-256 bcb1a018ba61…
View input schema
{
"type": "object",
"properties": {
"css_snippet": {
"type": "string",
"description": "Must be a non-empty CSS text snippet. Ignore unsupported at-rules gracefully and continue parsing what can be understood."
},
"html_snippet": {
"type": "string",
"description": "Must be a non-empty HTML text snippet. The tool must parse a static DOM tree from this input only."
},
"selected_element": {
"type": "string",
"description": "Must identify exactly one element in the provided HTML. Accept a CSS selector or element path string. If it matches zero or multiple elements, return a selection error."
},
"show_paint_order": {
"type": "boolean",
"description": "Boolean flag controlling whether the paint order trace is included in the result."
},
"show_stacking_context_chain": {
"type": "boolean",
"description": "Boolean flag controlling whether the stacking context chain is included in the result."
}
},
"required": [
"css_snippet",
"html_snippet",
"selected_element",
"show_paint_order",
"show_stacking_context_chain"
],
"additionalProperties": false
}
JSON Contract Compatibility Checker
json-contract-compatibility-checker
Developers need to confirm that a sample API response still matches a contract, including required fields, type expectations, enum constraints, and unexpected shape changes.
Schema valid · SHA-256 6c8ef1335d16…
View input schema
{
"type": "object",
"properties": {
"contract_json": {
"type": "string",
"description": "Must be valid JSON text. The contract must be an object. Supported contract keys are name/title, type, required, properties, items, enum, const, additionalProperties, and nested combinations of those. Missing or invalid JSON must produce a parse error."
},
"sample_json": {
"type": "string",
"description": "Must be valid JSON text. The sample must be a JSON object, array, string, number, boolean, or null. Missing or invalid JSON must produce a parse error."
},
"show_path_details": {
"type": "boolean",
"description": "When true, mismatch outputs must include explicit JSONPath-like paths such as $.user.name. When false, the report may summarize issues without omitting the required output lists."
},
"strict_mode": {
"type": "boolean",
"description": "When true, extra paths not allowed by the contract are reported as mismatches whenever additionalProperties is false or omitted for object branches that define properties. When false, extra paths are still listed in extra_paths but do not change overall compatibility unless another required rule fails."
}
},
"required": [
"contract_json",
"sample_json",
"show_path_details",
"strict_mode"
],
"additionalProperties": false
}
JSON Schema Drift Impact Checker
json-schema-drift-impact-checker
API and frontend engineers need to know whether a JSON schema change will break real payloads, generated clients, or form bindings before they ship it.
Schema valid · SHA-256 04938269bd99…
View input schema
{
"type": "object",
"properties": {
"old_json_schema": {
"type": "string",
"description": "Must be valid JSON text representing the previous schema version. The schema must parse as an object; if parsing fails, show a parse error and stop comparison."
},
"new_json_schema": {
"type": "string",
"description": "Must be valid JSON text representing the proposed schema version. The schema must parse as an object; if parsing fails, show a parse error and stop comparison."
},
"sample_payloads": {
"type": "string",
"description": "Optional JSON text. Accept a single JSON value, an array of JSON values, or newline-separated JSON values. Blank input means no sample payload analysis."
},
"show_path_details": {
"type": "boolean",
"description": "Boolean toggle. When true, path-level findings must include explicit JSON Pointer style paths and short evidence notes."
},
"strict_mode": {
"type": "boolean",
"description": "Boolean toggle. When true, treat any added required constraint, narrowed type, removed enum option, reduced allowed array/object shape, or newly forbidden property as breaking."
}
},
"required": [
"old_json_schema",
"new_json_schema",
"show_path_details",
"strict_mode"
],
"additionalProperties": false
}
Multipart Form Data Inspector
multipart-form-data-inspector
Frontend and API developers need to see exactly what a browser will send as multipart form data, because hidden controls, disabled fields, repeated names, and file inputs often create payload mismatches.
Schema valid · SHA-256 f57c5ca728be…
View input schema
{
"type": "object",
"properties": {
"html_form_snippet": {
"type": "string",
"description": "Must contain a single HTML <form> snippet or a fragment that includes one form element. Empty input is invalid. The tool must parse markup locally only."
},
"control_state_overrides": {
"type": "string",
"description": "Must be valid JSON text describing per-control state overrides such as value, checked, selected, disabled, or files. If empty, treat as an empty object. Invalid JSON must produce a parse error state and no preview."
},
"expected_field_list": {
"type": "string",
"description": "Must be a newline-separated or comma-separated list of expected field names, or an empty string. Names are compared case-sensitively and after trimming surrounding whitespace."
},
"selected_submitter": {
"type": "string",
"description": "Must be a submit control identifier such as a control name, id, or CSS-like path token understood by the parser, or an empty string to indicate no explicit submitter. If the selector matches multiple submitters, this is an error."
},
"submission_mode": {
"type": "string",
"enum": [
"multipart/form-data",
"form-data-preview-only"
],
"description": "Must be one of the supported deterministic modes. multipart/form-data computes browser-like multipart serialization metadata and field ordering; form-data-preview-only suppresses boundary rendering while preserving field ordering and inclusion rules."
}
},
"required": [
"html_form_snippet",
"control_state_overrides",
"expected_field_list",
"selected_submitter",
"submission_mode"
],
"additionalProperties": false
}
Spreadsheet Merge Conflict Reconciler
spreadsheet-merge-conflict-reconciler
Teams need to reconcile two spreadsheet versions and see what changed, what conflicts, and which rows or columns need manual review.
Schema valid · SHA-256 f09950e5c58b…
View input schema
{
"type": "object",
"properties": {
"sheet_a": {
"type": "string",
"description": "Paste or upload the first sheet snapshot as tabular text. Accept CSV-style or TSV-style rows with a header row. Must contain at least one data row and one header row."
},
"sheet_b": {
"type": "string",
"description": "Paste or upload the second sheet snapshot as tabular text. Accept CSV-style or TSV-style rows with a header row. Must contain at least one data row and one header row."
},
"match_keys": {
"type": "string",
"description": "Provide one or more column names used to match rows between Sheet A and Sheet B. Separate multiple keys with commas, semicolons, or new lines. Each key must exist in both sheets after normalization."
},
"case_sensitive": {
"type": "boolean",
"description": "When false, row key matching and field comparisons ignore letter case. When true, comparisons preserve letter case exactly."
},
"trim_whitespace": {
"type": "boolean",
"description": "When true, leading and trailing whitespace is removed from headers, keys, and cell values before matching and comparison. Internal spaces are preserved."
}
},
"required": [
"sheet_a",
"sheet_b",
"match_keys",
"case_sensitive",
"trim_whitespace"
],
"additionalProperties": false
}
Webhook Payload Shape Sanity Checker
webhook-payload-shape-sanity-checker
Developers need to verify that webhook events preserve required fields, nesting, and array shapes across example payloads before wiring integrations.
Schema valid · SHA-256 309acdcbdc6e…
View input schema
{
"type": "object",
"properties": {
"payload_samples": {
"type": "string",
"description": "Accept one or more JSON payload samples as pasted text. Each sample must parse as valid JSON. Multiple samples may be separated by blank lines or labeled blocks. Empty input is invalid."
},
"expected_shape_json": {
"type": "string",
"description": "Accept a JSON object describing the required webhook shape. Must parse as valid JSON and represent an object or array-shaped contract. Empty input is invalid."
},
"strict_mode": {
"type": "boolean",
"description": "When true, any missing required path, type mismatch, enum mismatch, array shape mismatch, or extra top-level path outside permissive rules marks the result incompatible."
},
"show_path_details": {
"type": "boolean",
"description": "When true, output includes JSON-pointer-like paths for every mismatch and extra field. When false, only summarized path groups are required in the output."
}
},
"required": [
"payload_samples",
"expected_shape_json",
"strict_mode",
"show_path_details"
],
"additionalProperties": false
}