deadline-feasibility
Can this plan of steps finish inside the remaining time, in the expected case and the worst case? — Takes steps with expected and worst-case durations, dependencies (steps with no dependency between them run in parallel), retries with backoff, and the time remaining, and computes the critical path for both cases. Verdict guaranteed (worst case fits: pass), likely (only the expected case fits: unknown) or infeasible (even the expected case does not fit: fail), with the slack and the critical-path
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": {
"steps": "<steps>",
"remainingMs": "<remainingMs>"
},
"name": "deadline-feasibility"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| steps | Yes | ||
| overheadMs | No | Fixed time to reserve for settlement, serialization, etc. | |
| remainingMs | Yes | Time left to the hard deadline, measured by the caller. |