Shiftyasan MCP Server

Validate Shiftyasan solver input

validate_shift_input

Validate a shift solver request payload against the Shiftyasan public API schema to confirm correctness before running solve_shift. Returns validation summary or field-level errors.

Instructions

Validate a shift solver request payload against the Shiftyasan public API schema. Free of charge (does not run the solver). Use this before solve_shift to confirm the request shape is correct, especially when constructing the payload programmatically. Returns either {valid: true, ...summary} or an RFC 7807 problem detail with field-level errors.

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": {
      "request": "<request>"
    },
    "name": "validate_shift_input"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes	The full SolveRequest payload (schedule_period, shifts, duties, employees, constraints, options). Schema: GET <base URL>/v1/public/openapi.json (base URL = SHIFTYASAN_BASE_URL, default https://api.shiftyasan.com).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that the tool is 'Free of charge (does not run the solver),' implying no side effects, and describes the return format: '{valid: true, ...summary} or an RFC 7807 problem detail.' This provides solid transparency, though it doesn't elaborate on potential errors or rate limits.

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?

The description is three sentences, front-loaded with purpose, then usage guidance, and then return format. Every sentence earns its place with no redundancy or fluff.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers everything needed: purpose, usage, behavior, and return value. It points to the external schema for the full payload structure, making it complete for the target use case.

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 input schema already provides 100% coverage of the single parameter (`request`) with a detailed description pointing to the OpenAPI schema. The tool description adds no extra parameter-level meaning, so baseline 3 is appropriate.

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 clearly states the tool's function: 'Validate a shift solver request payload against the Shiftyasan public API schema.' It uses a specific verb ('validate') and resource ('shift solver request'), and distinguishes itself from siblings by noting 'does not run the solver' and pointing to usage before `solve_shift`.

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

Usage Guidelines5/5

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

The description explicitly says when to use it: 'Use this before `solve_shift` to confirm the request shape is correct, especially when constructing the payload programmatically.' This names the alternative tool and provides clear contextual guidance.

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

Deploy Server