Skip to main content
Glama

Edit shifts

edit_shifts
Destructive

Use this when the user adds, moves, reassigns, retimes or deletes specific shifts in one week. Shift ids are the ids in the week results. Every date must fall inside the week given by week_start.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "edit_shifts"
  }
}

Input Schema

NameRequiredDescriptionDefault
addNo
removeNoShift ids to delete.
updateNo
week_startNoWhich week: "this", "next" or "last" (counted from today in the workplace's time zone), or any date in that week as YYYY-MM-DD. Omit for this week. For next week pass "next".
workplace_idNoWorkplace id. Omit to use the first workplace.

Output Schema

NameRequiredDescriptionDefault
fillNo
weekYes
laborYes
linksYes
staffYes
checksYes
noticeYes
shiftsYes
totalsYes
accountYes
coverageYes
requestsNoTime-off requests from staff waiting for an answer
workplaceYes
schemaVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description is consistent by saying it deletes shifts. It adds valuable behavioral constraints—shift ids come from week results and every date must fall inside week_start—but does not disclose atomicity or partial-failure behavior.

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?

Two sentences are front-loaded with the usage trigger and the most important constraints. There is no filler or redundant restatement.

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

Completeness4/5

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

Annotations cover the destructive safety profile and an output schema exists, so the description need not explain return values. It supplies the key scoping and id constraints for a bulk mutation, though it omits some operational details like partial failure and update semantics.

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 description adds useful meaning for week_start and shift ids: dates must be inside the week, and ids come from week results. With 60% schema coverage and complex add/update/remove arrays, it still does not explain field-level update behavior, person versus staff_id, or how the arrays interact.

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 uses specific verbs—adds, moves, reassigns, retimes, deletes—and names the exact resource: specific shifts in one week. That scope distinguishes it from bulk week-level siblings like fill_week and copy_week.

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?

It gives a clear trigger: use when the user adds, moves, reassigns, retimes, or deletes specific shifts in one week. It does not explicitly state when not to use it or name sibling alternatives, so it falls short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources