Skip to main content
Glama

nws_public_witnessing_preview_shift_change

Preview public witnessing shift changes—add, edit, duplicate, copy, or remove location shifts before confirming. Removing a shift also deletes its reservations.

Instructions

Preview adding, editing, duplicating, copying, or removing location shifts.

operation is create, update, duplicate, delete, delete_all, or copy_from_location. values may set DayOfWeek (0 Sunday to 6 Saturday), StartTime and EndTime (HH:MM, or null), MaxPersons, and KeyPersons (0-7). Removing a shift also deletes all of its reservations.

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": {
      "operation": "<operation>",
      "location_id": "<location_id>"
    },
    "name": "nws_public_witnessing_preview_shift_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesNo
shift_idNo
operationYes
location_idYes
source_location_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations present the description carries the full burden, and it does deliver one genuinely valuable disclosure: deleting a shift cascades to all of its reservations. It says nothing about what a preview actually produces or persists, whether the result is committed later, or whether permissions are required for delete_all. One strong trait, several important gaps.

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?

Purpose is front-loaded in the first clause and the remaining sentences are dense with usable facts — no filler. The operation list is embedded mid-sentence rather than broken out, which makes it slightly harder to scan, but nothing is wasted.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the cascade note covers the riskiest behavior. Still, for a five-parameter tool with zero schema coverage the description omits the preview lifecycle and the meaning of shift_id and source_location_id, leaving the agent to guess at call sequencing.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it does for the two most complex parameters: it enumerates the operation values (create, update, duplicate, delete, delete_all, copy_from_location) and documents the values keys with formats (DayOfWeek 0–6, HH:MM or null, MaxPersons, KeyPersons 0–7). It leaves shift_id and source_location_id unexplained, though source_location_id is inferable from copy_from_location.

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

Purpose4/5

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

The opening sentence names a specific verb (Preview) and resource (location shifts) and enumerates the five mutation intents it covers. However, it never contrasts itself with the commit/cancel counterparts in the sibling set (e.g. nws_public_witnessing_preview_location_change), so the agent must infer the preview-vs-commit split from naming convention alone.

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?

"Preview" implies this is a non-committing first step, which gives implied usage guidance, but the description never states when to pick this over the location/template preview siblings, nor that a matching commit is required afterward. No exclusions or preconditions are given.

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

Deploy Server

Other Tools