How it works
Each task duration is perturbed independently within a uniform relative uncertainty range. Repeated scenarios produce a mean duration, empirical 95th percentile and fraction of scenarios meeting the budget.
Inputs and units
Pass selected durations, a time budget, sample count, seed and relative uncertainty. The direct tool accepts your own plan. The optional native composer uses a fixed sample count per candidate only when an exact duration bound is insufficient.
What the result contains
The probability estimate and duration summaries let an assistant compare a high-value plan with its sensitivity to delays. The output records the simulation assumptions.
Example MCP call
{
"name": "simulate_plan",
"arguments": {
"durations": [
60,
30
],
"budget": 120,
"samples": 10000,
"seed": 42,
"uncertainty": 0.25
}
}Send this tool name and arguments through a connected MCP client. Discover the authoritative input schema with tools/list.
Execution and availability
ScoreCompute exposes this tool through MCP Streamable HTTP. Rust computation runs on a connected worker; the public website and MCP gateway run separately. CUDA is implemented for simulate_pi; the other tools currently run on CPU. Requests are bounded and concurrent work may be refused when capacity is occupied.
Record inputs, assumptions and returned provenance when sharing a result. The public observatory displays software client names and tool activity, without publishing calculation arguments or results.