Toast MCP Server and API by Cotlet

Create shift in Toast

toast_create_shift

Read-onlyIdempotent

Create shift in the user's own Toast account from ChatGPT, Claude or any AI agent. Returns how to do it in Toast step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Toast Cloud Browser. Toast's official API: Toast has an API, but the access a restaurant creates for itself is read-only (checked 28 Oct 2026).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With readOnlyHint=true already declared, the description adds genuinely useful context: the tool performs no external action on its own and produces procedural guidance only. It also explains why the browser path exists (self-provisioned Toast API access is read-only), which preempts an agent trying an API route. The future-dated 'checked 28 Oct 2026' stamp reads oddly but doesn't mislead about behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core message is front-loaded, but the single long sentence chains three ideas and the trailing API-access sentence is secondary justification rather than actionable guidance. It is not padded, but it could be restructured into a clearer two-beat statement of output and next step.

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

Completeness4/5

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

No output schema exists, and the description compensates by describing the return value as step-by-step screens, buttons, and fields. For a zero-parameter, non-mutating planning tool this is close to sufficient; it only lacks a note on whether the returned steps are account-specific or generic.

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?

The tool takes zero parameters, so the baseline is 4 and the description does not need to explain inputs. It correctly implies nothing is passed in to scope the shift details, which the agent supplies to the browser tools instead.

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?

Names a specific verb and resource ('Create shift') and immediately clarifies the tool's actual output: a step-by-step guide for Toast, not an executed write. This distinguishes it from cotlet_browser_* siblings, which it names as the actual execution path. The only shortfall is that it never contrasts with the sibling toast_publish_shifts, which is the nearest look-alike operation.

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

Usage Guidelines4/5

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

Explicitly states the workflow split: this tool returns instructions and 'opens nothing by itself,' then the agent uses cotlet_browser_* tools to perform the steps. That is a clear when-to-use and when-not-to-use signal. It does not cover sequencing with toast_publish_shifts or whether to re-call after a failure.

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

All Toast MCP Server and API by Cotlet tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?