Stratum Shifts

Fill week

fill_week

Use this when the user wants open shifts filled. Assigns people to every open shift and every uncovered shift the workplace needs, within each person's roles, availability, dates off, hour limit and rest rules, sharing hours, weekends and closes fairly. It never moves or removes existing shifts. For any shift it cannot fill it names the people closest to taking it and what stops each.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "week_start": "<week_start>"
    },
    "name": "fill_week"
  }
}

Input Schema

Name	Required	Description	Default
`week_start`	Yes	The week to fill: "this", "next" or "last" (counted from today in the workplace's time zone), or any date in that week as YYYY-MM-DD. For next week pass "next".
`workplace_id`	No	Workplace id. Omit to use the first workplace.

Output Schema

Name	Required	Description
`fill`	No
`week`	Yes
`labor`	Yes
`links`	Yes
`staff`	Yes
`checks`	Yes
`notice`	Yes
`shifts`	Yes
`totals`	Yes
`account`	Yes
`coverage`	Yes
`requests`	No	Time-off requests from staff waiting for an answer
`workplace`	Yes
`schemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only declare it is a non-read-only, non-idempotent, non-destructive mutation. The description adds substantial context: the constraints it honours (roles, availability, hours, rest, fairness), that existing shifts are never touched, and that unfillable shifts return the closest candidates plus blocking reasons.

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

Conciseness5/5

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

Four sentences, front-loaded with the trigger, then behaviour, then the non-destructive guarantee, then the failure-reporting behaviour. Nothing is redundant.

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?

For a constrained scheduling mutation with an output schema, the agent has the trigger, the constraint model, the safety boundary, and what happens on partial failure. No further detail is needed to call it correctly.

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?

Schema description coverage is 100%, so week_start's accepted formats and workplace_id's default are already fully documented. The description adds no parameter-level detail, so the baseline 3 applies.

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?

Specific verb (fills/assigns) plus precise scope: every open and uncovered shift in a week, subject to a named set of constraints. It is easily told apart from edit_shifts and find_cover by the 'fills every open shift' framing.

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

Usage Guidelines4/5

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

The opening clause gives a clear trigger ('when the user wants open shifts filled') and 'It never moves or removes existing shifts' implicitly excludes the edit_shifts case. It stops short of naming a sibling alternative explicitly, so it is strong but not quite the full when/when-not/alternative statement.

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

All Stratum Shifts tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?