run_vander_checks
Run VANDER QA checks for a single requestId to validate API endpoint behavior and return per-check pass/fail results, evidence, and failure details.
Instructions
Execute the automatic VANDER checks for one requestId. Returns one row per check (id, whose prefix is the axis; result pass/fail/skipped; detail with the evidence) and failures with expected/actual/body snippet. Probes vary method, credentials and body; they never capture variables or replace the session's last response. State-changing probes (any POST/PUT/PATCH/DELETE) are skipped unless includeDestructive is true — ask the user before enabling it. maxDurationMs is the budget for the Responsiveness check.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"definitionRelativePath": "<definitionRelativePath>",
"requestId": "<requestId>"
},
"name": "run_vander_checks"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| axes | No | Limit to these VANDER axes (default: all six). | |
| requestId | Yes | ||
| timeoutMs | No | ||
| maxDurationMs | No | Budget for the Responsiveness check. | |
| workspaceRoot | No | Optional when MCP_WORKSPACE_ROOT is set. | |
| includeDestructive | No | Also send state-changing probes (POST/PUT/PATCH/DELETE). | |
| definitionRelativePath | Yes | e.g. .mcp/api/default.yaml |