Skip to main content
Glama

get_rosters_preload

Fetch a month's personal roster preload in one API call, covering shift requests, vacant duties, shift swaps, and absences.

Instructions

Returns the personal roster preload for one month. A single API call that covers multiple areas: Einsatzwünsche, Vakante Dienste, and Diensttausch.

Returns raw API data with these top-level keys: { rosterUrlaubEinsatzwunsch: { // personal calendar + shift requests data: { data: [{ item1: { name, id }, // employee (self) item2: { data: [{ // all days of the month (not sparse) day: { date, bankHolidayName, isSchoolHoliday }, shortName, // duty type label shortNameSollplan, // concrete duty code, e.g. "H31T" einsatzwunsch: boolean, // true = shift request exists for this day prioritaet: boolean, beantragt: boolean, // requested genehmigt: boolean, // approved einsatzwunschWunsch: number, // wish priority level kommentar: string }]} }]} },

swapDutyOffersOffered: { // Diensttausch: offers from others (can accept) data: { offers: [{ id, date, offerer, acceptor, dutiesOfferer: { data: [string] }, dutiesAcceptor: { data: [string] }, workstationsOfferer, planninggroupsOfferer, workstationsAcceptor, planninggroupsAcceptor, state, comment }]} },

swapDutyOffersOwn: { // Diensttausch: own offers data: { offers: [...] } },

vacantDutiesOccupied: { // Vakante Dienste: taken on by employee data: { duties: [{ idVacantDuty, atDate, nameWorkstation, duty, occupyUntil, state, comment, isAssumed, idPlanningGroup, namePlanningGroup }], legendDuties: { ... } } },

vacantDutiesAssumed: { // Vakante Dienste: assumed but pending data: { duties: [...] } },

fehlzeiten: { ... } // absences }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesYear, e.g. 2026
monthYesMonth (1–12)
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and provides substantial behavioral context: it states that the API call is single-call covering multiple areas, returns 'raw API data', and explicitly notes that the days list is 'not sparse' (all days included). It also details the structure of each response section. However, it does not mention permissions, error handling, or side effects, which would have made it more complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but exceptionally structured: the first sentence states purpose, and the rest is a well-organized code block with comments explaining each top-level key and nested fields. Every section earns its place given the absence of an output schema. It could be slightly trimmed, but the density of useful information justifies the length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of an output schema, the description thoroughly documents the return value with nested structures, making the tool's behavior fully understandable. It covers all major response areas (calendar, swap offers, vacant duties, absences). Error handling and pagination are not discussed, but for a single-call preload with a clearly defined output, the description is sufficiently complete for an agent to select and invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides descriptions for both parameters (year and month) with 100% coverage. The description adds no additional meaning beyond confirming the tool targets 'one month', which aligns with year/month but does not enrich the parameter semantics. Baseline 3 applies because schema coverage is high.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states what the tool does: 'Returns the personal roster preload for one month' and lists the specific areas it covers (Einsatzwünsche, Vakante Dienste, Diensttausch). This is a specific verb+resource+scope that distinguishes it from siblings like get_planungsgruppen or get_vakante_duty_details, which are narrower in focus.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies it is a single combined call for a month's personal roster, but does not explicitly state when to prefer it over alternatives or when not to use it. Sibling names suggest other tools for specific details, but no direct guidance is given. Usage context is implied rather than explicitly stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jalibu/careman-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server