Skip to main content
Glama
shiftyasan

Shiftyasan MCP Server

by shiftyasan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SHIFTYASAN_API_KEYYesBearer API key. Format: sk_(live|test)_<64 hex chars>.
SHIFTYASAN_BASE_URLNoOverride base URL (default https://api.shiftyasan.com). Useful for staging or self-host.https://api.shiftyasan.com

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
validate_shift_inputA

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.

solve_shiftA

Run the Shiftyasan solver on a shift scheduling request payload. Synchronous (returns within ~30 seconds for solver_timeout_seconds <= 30). Charged per call: requires SHIFTYASAN_API_KEY with sufficient quota. Tip: call validate_shift_input first to confirm the payload shape (free). See https://api.shiftyasan.com/v1/public/openapi.json for the request/response schema.

get_solve_jobA

Check the status of an asynchronous solve job created by solve_shift (202 response with job_id). Free of charge. status "running" means the solver is still working — wait ~15 seconds and call again (large problems typically finish within 2–7 minutes). "completed" includes the solution and usage; "failed" includes error.code (e.g. no_solution).

Prompts

Interactive templates invoked by user choice

NameDescription
plan_shiftWalk through building a staff schedule with Shiftyasan: gather the requirements, validate them, solve, and present the roster in a form a shift manager can check.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct and non-overlapping purpose: validating input, running the solver, and checking async job status. There is no ambiguity in selecting between them.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores: validate_shift_input, solve_shift, get_solve_job. The naming is uniform and predictable.

Tool Count5/5

Three tools is a well-scoped set for a specialized solver API, covering validation, synchronous invocation, and asynchronous status retrieval without bloat or unnecessary redundancy.

Completeness5/5

The tool surface covers the full workflow: validate payload, run solver, and retrieve async result. There are no obvious missing operations for the stated domain of shift scheduling solving.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources