Build a full weekly timetable for a primary school (classes, teachers, rooms) via chat.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
The 8 input files, exactly as described in the interview guide's 'submission' and 'topics'. JSON files are sent as JSON text inside the string; empty CSV files contain only the header line.
Optional, for anonymous usage statistics: the school's country (e.g. 'Denmark') if the user has mentioned it. Never ask the user just for this.
Optional, for anonymous usage statistics: the language you talk to the user in (e.g. 'da', 'en'). Fill it in if you know it; never ask the user.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
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.
| Argument | Type | Description |
|---|---|---|
| files* | object | The 8 input files, exactly as described in the interview guide's 'submission' and 'topics'. JSON files are sent as JSON text inside the string; empty CSV files contain only the header line. |
| user_country | string | Optional, for anonymous usage statistics: the school's country (e.g. 'Denmark') if the user has mentioned it. Never ask the user just for this. |
| user_language | string | Optional, for anonymous usage statistics: the language you talk to the user in (e.g. 'da', 'en'). Fill it in if you know it; never ask the user. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"files"
],
"properties": {
"files": {
"type": "object",
"required": [
"skolekonfig",
"laerere",
"plan",
"min_dag",
"bindings",
"dagsstruktur",
"lokaler",
"minmax"
],
"properties": {
"plan": {
"type": "string",
"description": "Content of the 'plan' file as text (JSON or CSV, see the interview guide)"
},
"minmax": {
"type": "string",
"description": "Content of the 'minmax' file as text (JSON or CSV, see the interview guide)"
},
"laerere": {
"type": "string",
"description": "Content of the 'laerere' file as text (JSON or CSV, see the interview guide)"
},
"lokaler": {
"type": "string",
"description": "Content of the 'lokaler' file as text (JSON or CSV, see the interview guide)"
},
"min_dag": {
"type": "string",
"description": "Content of the 'min_dag' file as text (JSON or CSV, see the interview guide)"
},
"bindings": {
"type": "string",
"description": "Content of the 'bindings' file as text (JSON or CSV, see the interview guide)"
},
"skolekonfig": {
"type": "string",
"description": "Content of the 'skolekonfig' file as text (JSON or CSV, see the interview guide)"
},
"dagsstruktur": {
"type": "string",
"description": "Content of the 'dagsstruktur' file as text (JSON or CSV, see the interview guide)"
}
},
"description": "The 8 input files, exactly as described in the interview guide's 'submission' and 'topics'. JSON files are sent as JSON text inside the string; empty CSV files contain only the header line."
},
"user_country": {
"type": "string",
"maxLength": 60,
"description": "Optional, for anonymous usage statistics: the school's country (e.g. 'Denmark') if the user has mentioned it. Never ask the user just for this."
},
"user_language": {
"type": "string",
"maxLength": 20,
"description": "Optional, for anonymous usage statistics: the language you talk to the user in (e.g. 'da', 'en'). Fill it in if you know it; never ask the user."
}
}
}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.
No arguments.
{
"type": "object",
"properties": {}
}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, 'summary' = key figures and lists of classes/teachers only. Use 'names' to get only some classes/teachers (recommended for big schools). If impossible: the reasons.
| Argument | Type | Description |
|---|---|---|
| view | string | What to show when done (default 'classes') |
| names | array | Only these classes (e.g. '1.A') or teacher codes (e.g. 'T01') |
| job_id* | string | job_id from create_schedule or validate_input |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"job_id"
],
"properties": {
"view": {
"enum": [
"classes",
"teachers",
"summary"
],
"type": "string",
"description": "What to show when done (default 'classes')"
},
"names": {
"type": "array",
"items": {
"type": "string"
},
"description": "Only these classes (e.g. '1.A') or teacher codes (e.g. 'T01')"
},
"job_id": {
"type": "string",
"description": "job_id from create_schedule or validate_input"
}
}
}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, other personal data or the school's data files. Tell the user briefly that it was sent. Nobody replies through this channel - if the user wants an answer, give them the support email [email protected].
| Argument | Type | Description |
|---|---|---|
| job_id | string | job_id of the timetable the feedback is about, if any |
| message* | string | The user's feedback, without names or other personal data |
| sentiment | string | Overall tone of the feedback, if clear |
| user_country | string | Optional, for anonymous usage statistics: the school's country (e.g. 'Denmark') if the user has mentioned it. Never ask the user just for this. |
| user_language | string | Optional, for anonymous usage statistics: the language you talk to the user in (e.g. 'da', 'en'). Fill it in if you know it; never ask the user. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"message"
],
"properties": {
"job_id": {
"type": "string",
"maxLength": 40,
"description": "job_id of the timetable the feedback is about, if any"
},
"message": {
"type": "string",
"maxLength": 2000,
"minLength": 1,
"description": "The user's feedback, without names or other personal data"
},
"sentiment": {
"enum": [
"positive",
"negative",
"mixed"
],
"type": "string",
"description": "Overall tone of the feedback, if clear"
},
"user_country": {
"type": "string",
"maxLength": 60,
"description": "Optional, for anonymous usage statistics: the school's country (e.g. 'Denmark') if the user has mentioned it. Never ask the user just for this."
},
"user_language": {
"type": "string",
"maxLength": 20,
"description": "Optional, for anonymous usage statistics: the language you talk to the user in (e.g. 'da', 'en'). Fill it in if you know it; never ask the user."
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| files* | object | The 8 input files, exactly as described in the interview guide's 'submission' and 'topics'. JSON files are sent as JSON text inside the string; empty CSV files contain only the header line. |
| user_country | string | Optional, for anonymous usage statistics: the school's country (e.g. 'Denmark') if the user has mentioned it. Never ask the user just for this. |
| user_language | string | Optional, for anonymous usage statistics: the language you talk to the user in (e.g. 'da', 'en'). Fill it in if you know it; never ask the user. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"files"
],
"properties": {
"files": {
"type": "object",
"required": [
"skolekonfig",
"laerere",
"plan",
"min_dag",
"bindings",
"dagsstruktur",
"lokaler",
"minmax"
],
"properties": {
"plan": {
"type": "string",
"description": "Content of the 'plan' file as text (JSON or CSV, see the interview guide)"
},
"minmax": {
"type": "string",
"description": "Content of the 'minmax' file as text (JSON or CSV, see the interview guide)"
},
"laerere": {
"type": "string",
"description": "Content of the 'laerere' file as text (JSON or CSV, see the interview guide)"
},
"lokaler": {
"type": "string",
"description": "Content of the 'lokaler' file as text (JSON or CSV, see the interview guide)"
},
"min_dag": {
"type": "string",
"description": "Content of the 'min_dag' file as text (JSON or CSV, see the interview guide)"
},
"bindings": {
"type": "string",
"description": "Content of the 'bindings' file as text (JSON or CSV, see the interview guide)"
},
"skolekonfig": {
"type": "string",
"description": "Content of the 'skolekonfig' file as text (JSON or CSV, see the interview guide)"
},
"dagsstruktur": {
"type": "string",
"description": "Content of the 'dagsstruktur' file as text (JSON or CSV, see the interview guide)"
}
},
"description": "The 8 input files, exactly as described in the interview guide's 'submission' and 'topics'. JSON files are sent as JSON text inside the string; empty CSV files contain only the header line."
},
"user_country": {
"type": "string",
"maxLength": 60,
"description": "Optional, for anonymous usage statistics: the school's country (e.g. 'Denmark') if the user has mentioned it. Never ask the user just for this."
},
"user_language": {
"type": "string",
"maxLength": 20,
"description": "Optional, for anonymous usage statistics: the language you talk to the user in (e.g. 'da', 'en'). Fill it in if you know it; never ask the user."
}
}
}