Rotase
Employee scheduling, staffing feasibility, localized demos, schedule reports and CSV export.
| Endpoint | https://rotase.com/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 8 tools · grade D (55) · pin ts_d5247c35ecbd048ce2a7c9aa265b0b02 · protocol 2025-03-26 |
| First / last listed | 2026-11-01 02:37 UTC / 2026-11-01 02:37 UTC |
| Grade over time | 2026-11-01: D (55), 8 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: rotase_health rotase_examples rotase_create_demo_project rotase_validate_project rotase_generate_schedule rotase_check_feasibility rotase_schedule_report rotase_export_csv
rotase_health | Read-only check that the Rotase scheduling service is available. Use this when connectivity or service availability is uncertain. It does not require a project and does not change data. params: none |
rotase_examples | Read an example store, employees and complete project payload. Defaults to English labels; pass a supported language code to localize names. Call this when the project structure or field names are unknown. The returned project can be copied and edited before validation. This operation is read-only and does not access a user browser or saved project. params: language |
rotase_create_demo_project | Create a localized demonstration project using the same project-creation operation as the Rotase API. The server chooses the current period in the requested timezone, loads the localized demo names and company name, applies the selected country calendar and can generate an initial schedule. The result is returned in the response; nothing is saved on the server or in a browser. params: country, region, language, timezone, kind, closeOnHolidays |
rotase_validate_project | Validate a complete Rotase project payload without saving or modifying it. Use rotase_examples first if the payload shape is unknown. Call this before feasibility checks or schedule generation. The input is the project object itself, not a wrapper with an additional "project" property. params: schemaVersion, project*, store*, employees*, availability, preferences, monthlyTargets, schedules |
rotase_generate_schedule | Generate a monthly employee schedule from a complete Rotase project payload. Use rotase_examples to obtain a template, then rotase_validate_project first. The operation calculates and returns a schedule; it does not save a project, modify browser storage or create an account. Explain returned violations or shortages instead of assuming that every project is schedulable. params: schemaVersion, project*, store*, employees*, availability, preferences, monthlyTargets, schedules |
rotase_check_feasibility | Check whether a complete Rotase project can satisfy opening hours, staffing requirements, availability, rest rules and work-hour limits. Use after rotase_validate_project and before generation when the user asks whether a schedule is possible. This operation is read-only and does not save or modify the project. params: schemaVersion, project*, store*, employees*, availability, preferences, monthlyTargets, schedules |
rotase_schedule_report | Calculate per-store and per-employee statistics for a generated monthly schedule. Pass the complete project object and either provide the generated schedule as the top-level "schedule" property or put it in the project schedules array. This operation is read-only and does not save data. params: schemaVersion, project*, store*, employees*, availability, preferences, monthlyTargets, schedules |
rotase_export_csv | Export a generated monthly schedule as spreadsheet-compatible CSV. Pass the complete project object and either provide the generated schedule as the top-level "schedule" property or put it in the project schedules array. The response contains the CSV text; nothing is saved on the server. params: schemaVersion, project*, store*, employees*, availability, preferences, monthlyTargets, schedules |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.