planner
Compute real duty rosters from your AI assistant - rule-based vigotime planner, API key or OAuth.
Should I use this
Quality & Safety
Findings (2)
- LOWin solve_result
- LOWin account_balance
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"planner": {
"url": "https://api.vigotime.com/mcp"
}
}
}Remote endpoints
https://api.vigotime.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (6)
🟡solve_submit(payload)
Reicht einen Dienstplan-Solve-Job ein. `payload` ist der self-contained Request: Pflicht: start_date, end_date (ISO), department {id}, employees [{id, contractHoursPerWeek, qualificationIds}], shifts [{id, departmentId, name, startTime, endTime, shiftType, minStaff}]. Optional u. a.: planning_rules, wishes, vacations, sick_leaves, holiday_dates, locked_assignments, social_points, wish_costs, config {timeout_seconds}. vacations darf Termine NACH end_date enthalten — noetig bei Datums-Kopplungsregeln mit Block-Tagen hinter dem Fenster (siehe Instructions). Datenschutz: IDs statt Namen verwenden. Antwort: {job_id, status}.
Input Schema
{
"type": "object",
"properties": {
"payload": {
"additionalProperties": true,
"title": "Payload",
"type": "object"
}
},
"required": [
"payload"
],
"title": "solve_submitArguments"
}Output Schema
{
"type": "object",
"additionalProperties": true,
"title": "solve_submitDictOutput"
}⚪solve_status(job_id)
Status eines Solve-Jobs (pending/running/completed/failed) inkl. Fortschritt.
Input Schema
{
"type": "object",
"properties": {
"job_id": {
"title": "Job Id",
"type": "string"
}
},
"required": [
"job_id"
],
"title": "solve_statusArguments"
}Output Schema
{
"type": "object",
"additionalProperties": true,
"title": "solve_statusDictOutput"
}⚪solve_result(job_id)
Ergebnis eines fertigen Solve-Jobs: assignments [{employee_id, shift_id, date}], unassigned_shifts mit Begründung, Statistiken.
Input Schema
{
"type": "object",
"properties": {
"job_id": {
"title": "Job Id",
"type": "string"
}
},
"required": [
"job_id"
],
"title": "solve_resultArguments"
}Output Schema
{
"type": "object",
"additionalProperties": true,
"title": "solve_resultDictOutput"
}⚪account_balance
Aktuelles Token-Guthaben der eigenen Organisation (Solves kosten Tokens).
Input Schema
{
"type": "object",
"properties": {},
"title": "account_balanceArguments"
}Output Schema
{
"type": "object",
"additionalProperties": true,
"title": "account_balanceDictOutput"
}⚪service_info
Build-Stand des laufenden Planner-Service: version (fortlaufende Build-Nummer), gitCommit, buildTime (UTC). Fuer Support-Anfragen und um Ergebnisse einem Software-Stand zuzuordnen.
Input Schema
{
"type": "object",
"properties": {},
"title": "service_infoArguments"
}Output Schema
{
"type": "object",
"additionalProperties": true,
"title": "service_infoDictOutput"
}⚪example_payload(kind)
Ein sofort lauffähiger Beispiel-Payload für solve_submit. kind='simple' (1 Woche, 3 MA, 2 Schichten), kind='wishes' (Wünsche, Social Points, Wunschkosten) oder kind='rules' (ArbZG-Planungsregeln: 11 h Ruhe hart + max. 5 Folgetage — zeigt, wie Regeln den Plan formen; Param-Namen sind exakt, falsche werden still ignoriert).
Input Schema
{
"type": "object",
"properties": {
"kind": {
"default": "simple",
"title": "Kind",
"type": "string"
}
},
"title": "example_payloadArguments"
}Output Schema
{
"type": "object",
"additionalProperties": true,
"title": "example_payloadDictOutput"
}Community
Evidence