io.github.wilbek-source/timetable-builder · v1.0.0 · communication
School Timetable Builder is healthy: it completed an MCP handshake in 1805 ms and exposes 5 tools.
Build a full weekly timetable for a primary school (classes, teachers, rooms) via chat.
Endpoint: https://timetable-builder.wilbek.workers.dev/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 5 |
| Latency | 1805 ms |
| Last checked (UTC) | 2026-10-16T15:00:46.265Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-16T15:00:46.265Z | Healthy | 1805 |
get_interview_guide | Returns the interview guide: which questions to ask the user, default values, engine limits and the exact format of the 8 input files. Call this first. |
validate_input | Checks the 8 input files in a few seconds without creating a timetable: file structure, engine limits and a capacity analysis (enough teachers/time?). Returns VALID (with warnings) or INVALID (with reasons). Always run this before create_schedule. |
create_schedule | Starts calculating the full timetable from the 8 input files (validate them first). Returns a job_id at once; the calculation takes about 5-8 minutes. Then keep calling get_schedule_result with the job_id in the same reply until it is done. |
get_schedule_result | Gets the status or result of a job from create_schedule (or a slow validate_input). While running: progress. When done: a compact timetable as text plus a link (valid 1 hour) to the full JSON result. view='classes' (default) = one table per class, 'teachers' = one per teacher incl. preparation time, |
send_feedback | Passes the user's feedback about the timetable service on to its developer (what worked, what did not, wishes). Only call it when the user has said they want to give feedback, and send what the user said in their own words (you may shorten it; any language is fine). Never include teacher names, othe |