How it works
The calculation relates angular motion to transverse speed through v = ω × distance, with the angular rate converted to radians. A claimed speed can then be compared with the speed required at a claimed distance.
Inputs and units
Provide angular speed in degrees per second and distance or speed hypotheses. The tool exposes bounded parameter ranges through tools/list.
What the result contains
Speed-distance comparisons and profiles help an assistant explain what the observation would imply under each hypothesis.
Example MCP call
{
"name": "analyze_kinematics",
"arguments": {
"angular_speed_deg_per_s": 1,
"claimed_distance_km": 10,
"claimed_speed_kmh": 600
}
}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.