Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_shift_work_calendar

Calculate ISO-8601 calendar week (Kalenderwoche KW) and rotating shift schedule (3-Schicht, 4-Schicht, 2-Schicht, 24h Feuerwehr) for any target date.

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": "get_shift_work_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternNoShift system: 3-schicht, 4-schicht, 2-schicht, or feuerwehr
target_dateNoTarget date YYYY-MM-DD (default today)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It implies a deterministic, side-effect-free calculation and enumerates the supported shift systems, but says nothing about the return shape (KW integer vs. formatted string, shift label), how the rotation is anchored, or what 'any target date' means for out-of-range dates. Useful but incomplete behavioral context.

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?

One front-loaded sentence with zero filler: the action, the two outputs, and the supported shift systems all appear immediately. Nothing needs trimming.

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 two-parameter, read-only calculation tool with no output schema and full schema coverage, the definition supplies enough to select and 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 coverage is 100% and both parameters already document their allowed values and the 'default today' behavior. The description only restates the shift-system list already in the pattern enum, adding no new meaning such as casing/format tolerance or interaction between pattern and date.

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 ('Calculate') plus two concrete resources: the ISO-8601 calendar week (KW) and a rotating shift schedule from a named set of systems. No sibling tool overlaps, and an agent can tell exactly what it gets back conceptually without opening the schema.

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?

Usage is implied by the description — call it when you need a KW or a shift assignment for a given date. There is no explicit when-to-use vs. when-not guidance, no note about what happens if pattern is omitted, and no alternatives named (none exist among siblings, but the definition doesn't say so).

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