EasyShiftPlan MCP Bridge

Overview Schema Source Related Servers Discussions Admin

Run an isolated scheduling demo

run_public_demo

Run an anonymous fictional scheduling demo in one call to generate a proposed roster, coverage and constraint checks, preference exceptions, and a manager next step without login or setup.

Instructions

Run a complete, anonymous demo with a fictional team in a single call. No account, OAuth, login, session ID, token, workspace ID or setup call is required. The result includes a proposed roster, coverage and hard-constraint checks, soft-preference exceptions and a manager next step. Each call is isolated; its schedule is not saved or published. If an instruction is ambiguous, return the blocker rather than silently ignoring it. Use fictional information only.

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

Input Schema

Name	Required	Description	Default
`demands`	No	Optional explicit fictional shift requirements. Each row can include day, role, start, end, shift, and required or min_required/max_required headcount. Omit to use sample shifts.
`industry`	No	Business type used to select the fictional sample team and shift templates.	restaurant
`team_size`	No	Number of synthetic workers, from 4 to 12; defaults to the selected industry's sample size.
`period_mode`	No	Schedule length: week or month. Defaults to one week.	week
`period_start`	No	Optional date in YYYY-MM-DD format inside the requested week or month; otherwise the next full period is selected.
`manager_request`	No	Optional natural-language scheduling instructions for this fictional team only. Ambiguous requests stop for review; never include real staff or business data.
`coverage_per_shift`	No	Workers required on each enabled shift for each operating day.
`time_limit_seconds`	No	Solver time budget, from 0.1 to 10 seconds. Defaults to 2 seconds.
`operating_days_per_week`	No	Number of open days, starting Monday. For example, 5 means Monday through Friday.

Output Schema

Name	Required	Description	Default
`demo`	Yes
`store`	Yes
`period`	Yes
`privacy`	No
`scenario`	Yes
`workflow`	Yes
`quality_check`	Yes
`parsed_request`	No
`schedule_preview`	Yes
`proposed_settings`	No
`feedback_next_step`	No
`optional_discovery`	No
`optional_next_steps`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only say readOnlyHint=false, idempotentHint=false, destructiveHint=false; the description adds the crucial context that each call is isolated and its schedule is 'not saved or published', which explains the non-read-only-but-non-destructive annotation combination. It also enumerates the returned artifacts (roster, coverage and hard-constraint checks, soft-preference exceptions, manager next step) and the ambiguity-handling policy.

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?

Purpose and the anonymity guarantee are front-loaded, and every sentence carries information. The auth enumeration ('No account, OAuth, login, session ID, token, workspace ID or setup call') is slightly padded but effectively preempts an agent's most likely false assumption.

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?

An output schema exists, so return values need not be exhaustively explained, yet the description still summarizes the payload shape. Combined with the isolation and fictional-data guarantees, an agent has enough to call it correctly; only explicit alternative-routing guidance is missing.

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?

Schema description coverage is 100% across all 9 parameters, so the schema already documents format, defaults and ranges (e.g. team_size 4-12, time_limit_seconds 0.1-10, period_mode week/month). The description adds no parameter-level detail beyond general intent, so the baseline of 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 opens with a specific verb+resource ('Run a complete, anonymous demo with a fictional team in a single call') and states scope precisely: isolated, no persistence, no auth. It is clearly distinguishable from siblings like submit_demo_feedback or prepare_share_draft, which are feedback- and sharing-oriented.

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?

It gives strong prerequisites ('No account, OAuth, login, session ID, token, workspace ID or setup call is required') and a clear usage constraint ('Use fictional information only'), plus behavior for ambiguous input ('return the blocker rather than silently ignoring it'). It does not explicitly name sibling alternatives or say when not to use this tool, so it stops short of a 5.

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

Deploy Server