site

Shift Pattern Generator: the site's own MCP server — calculator, enquiry (enquiry = a human...

Should I use this

Quality & Safety

B
Description quality
100%
Schema completeness
56%
Naming quality
88%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~765Tokens (tool definitions)
~928 BTypical response size
Moderate attention impact (0.60% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "site": {
      "url": "https://shiftpatterngenerator.co.uk/mcp"
    }
  }
}

Remote endpoints

https://shiftpatterngenerator.co.uk/mcpstreamable-http

What it can do

Tool inventory

Tools (5)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢calculator_describe

The inputs this calculator takes (with units, ranges and defaults), the outputs it returns, and the assumptions and tables behind it.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢calculate(onDays, offDays, shiftHours, coverHours, nightWork)

Run the Shift pattern generator calculator: Cycle length in days; Average working hours a week; Hours a week under the 48 hour average limit; Crews needed to cover the operation. Missing inputs fall back to their documented defaults.

Input Schema

{
  "type": "object",
  "properties": {
    "onDays": {
      "type": "number",
      "minimum": 1,
      "maximum": 14,
      "description": "Days on in one cycle",
      "default": 4
    },
    "offDays": {
      "type": "number",
      "minimum": 1,
      "maximum": 14,
      "description": "Days off in one cycle",
      "default": 4
    },
    "shiftHours": {
      "type": "number",
      "minimum": 4,
      "maximum": 16,
      "description": "Paid hours in one shift",
      "default": 12
    },
    "coverHours": {
      "type": "number",
      "minimum": 4,
      "maximum": 24,
      "description": "Hours a day the operation must be covered",
      "default": 24
    },
    "nightWork": {
      "type": "string",
      "enum": [
        "none",
        "night",
        "hazard"
      ],
      "description": "Does the pattern include night work?",
      "default": "night"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡enquiry_describe

Read first. States plainly what submit_enquiry does on Shift Pattern Generator: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡enquiry_fields

Every field of the Shift Pattern Generator enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡submit_enquiry(answers, consent, confirmation)

Submits an enquiry to Shift Pattern Generator — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Happy for my details to go to rota and workforce scheduling suppliers, who'll contact me directly."

Input Schema

{
  "type": "object",
  "properties": {
    "answers": {
      "type": "object",
      "additionalProperties": {
        "type": [
          "string",
          "number",
          "boolean"
        ]
      },
      "description": "the person's answers, keyed by field key"
    },
    "consent": {
      "type": "boolean",
      "description": "true only when the person has agreed to: Happy for my details to go to rota and workforce scheduling suppliers, who'll contact me directly."
    },
    "confirmation": {
      "type": "string",
      "description": "the confirmation token from step 1, after the person has approved the summary"
    }
  },
  "required": [
    "answers",
    "consent"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded5 tools
verifiedversion not recorded5 tools