Skip to main content
Glama

Quinyx MCP Server and API by Cotlet

Create shift in Quinyx

quinyx_create_shift
Read-onlyIdempotent

Create shift in the user's own Quinyx account from ChatGPT, Claude or any AI agent. Returns how to do it in Quinyx step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Quinyx Cloud Browser. Quinyx's official API: Quinyx has a REST API (checked 22 Oct 2026), but no official MCP server, and the API leaves out the manager's daily work: it cannot approve requests, offer shifts, attest hours or publish a schedule.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

The description clarifies the execution behavior, stating the tool 'opens nothing by itself' and 'Returns how to do it' rather than executing the database transaction. This is crucial context, especially given the `readOnlyHint` annotation.

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?

While the description is long, every sentence adds critical, non-redundant context regarding scope, implementation, and API limitations. The information is logically segmented.

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?

The description is highly complete. It defines the operational environment, the input source (AI agent), the output format (steps/fields), and the functional limitations relative to the broader Quinyx management system.

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?

Since this is a 0-parameter tool, the description does not need to elaborate on input schemas. It provides sufficient context regarding its intended use as a general instructional guide.

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 defines the tool's function ('Create shift in the user's own Quinyx account') and differentiates its operational model by specifying that it generates step-by-step instructions, not direct execution.

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?

It provides explicit guidance on scope by stating it serves as a guide for the user to then perform the action via `cotlet_browser_*` tools. It also clearly delineates what the tool cannot do, such as approving, offering, or publishing shifts, contrasting it with a theoretical official API.

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