Logs & Sharing
Tool-call History Validator
Check parallel tool calls, result IDs, duplicates, unresolved calls and message ordering.
Processed on our CPU server.Submitted input is processed for this run and is not stored.
1024 KiB limitInput
Result
A useful result starts here.
Paste your input or load an example,
then run the tool.
Supported formats & limitations
- Supply a Chat Completions messages array using assistant tool_calls with type function and tool results with tool_call_id. Legacy function_call and other provider formats are unsupported.
- Parallel results may arrive in any order; every pending call must receive a result before the next non-tool message. IDs must be non-empty and unique in the capture.
- Function arguments must be a string encoding a JSON object. This checks message structure and ordering, not tool behavior or argument schemas.
- Maximum 2,000 messages and 2,000 calls; depth 48 and 24,000 nodes. At most 200 findings, with truncation declared.
- Partial capture makes unknown calls/missing terminal results warnings. Proven ordering errors and duplicates remain errors.
Execution budget: 5s; output limit: 4096 KiB. Browser worker startup has a separate 3s allowance.