check_trace_readiness
Check an execution trace for evidence readiness, reporting per requirement if evidence for post-hoc causal reconstruction is met, partially met, or unmet, naming missing fields and span kinds.
Instructions
Check an agent execution trace against the evidence-readiness specification and report, per requirement, whether the evidence a post-hoc causal reconstruction would need is met, partially met, or unmet — naming the specific missing field and the span kind it belongs on. Accepts a file/directory path OR inline JSON content (exactly one). Runs entirely locally in this process; nothing is transmitted or persisted, and inline content is processed in memory only. This tool NEVER determines whether a failure occurred: it answers "does this trace contain what a reconstruction of class X would require," never "did class X occur." A fabricated-but-internally-consistent trace passes. This tool verifies evidence is present, not that it is true, and its result must never be relayed as "this agent is safe".
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "check_trace_readiness"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| trace_path | No | Path to a trace .json file or a directory of traces (*manifest.json excluded). | |
| require_class | No | Fold these classes' evidence requirements into the exit code (choices: config_drift, session_isolation_failure, cascade_contamination, prompt_injection). | |
| trace_content | No | A trace document as a JSON string, checked in memory and never written to disk. |