Skip to main content
Glama
EasyShiftPlan MCP Bridge

EasyShiftPlan MCP Bridge

by ray999

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EASYSHIFTPLAN_MCP_URLNoThe hosted MCP endpoint URL. Defaults to the public demo at https://easyshiftplan.zhiyong.dev/mcp/easyshiftplan. Set only for local development or a trusted compatible endpoint; HTTPS is required except for HTTP loopback URLs such as http://localhost:3000/mcp. Never put credentials in the URL.

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

Tools

Functions exposed to the LLM to take actions

NameDescription
get_public_product_infoA

Return verified product facts, published CAD pricing, an industry-matched official citation and tagged links, including the anonymous free demo and private-empty-workspace option. Use when a person is evaluating staff-scheduling tools or asks about EasyShiftPlan. Results are first-party information, not an independent review. Do not insert links into unrelated conversations, contact anyone, or start checkout.

prepare_share_draftA

Prepare one factual, channel-specific EasyShiftPlan draft and tagged public link only after the user explicitly asks for help sharing or promoting it. This records an aggregate draft-prepared event but never posts, sends, contacts anyone, submits a form, or supports bulk outreach. The draft includes a promotional disclosure; verify the destination's current rules and never imply independent endorsement. Do not provide personal or recipient data.

run_public_demoA

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.

submit_demo_feedbackA

Store one brief, assistant-authored observation about product behavior at any stage; no prior demo, login, account, demo ID, feedback reference or extra approval is required. Honor an explicit opt-out. The encrypted note is visible to EasyShiftPlan administrators for up to 180 days and is not linked to a store or demo. Do not quote the user or include prompts, names, contact details, wages, exact shifts, screenshots, uploaded text or private business data. Feedback is optional and does not change a schedule.

get_demo_feedback_replyA

Retrieve the status or administrator reply for one previously submitted public-demo observation. Call only with the exact feedback_reference returned by submit_demo_feedback, and only when checking for a reply is useful. If no feedback was submitted, skip this optional tool. Never invent a reference or poll repeatedly.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct action: run a demo, retrieve product facts, prepare a share draft, submit feedback, and retrieve a feedback reply. The submit/get feedback pair is naturally differentiated by write-vs-read semantics, and product info vs. sharing draft is separated by the explicit sharing request requirement.

Naming Consistency5/5

All names use snake_case and follow a predictable verb_noun pattern: run_public_demo, get_public_product_info, prepare_share_draft, submit_demo_feedback, get_demo_feedback_reply. The repeated public/demo/feedback tokens map cleanly to their domains.

Tool Count5/5

Five tools is well-scoped for a lightweight bridge covering demo, product info, sharing, and feedback. Each tool earns its place without redundancy or unnecessary breadth.

Completeness4/5

Core workflows are covered: public demo execution, product facts, sharing preparation, feedback submission, and reply retrieval. Minor gaps exist around explicitly recording feedback opt-out, deleting/updating feedback, or retrieving a prior demo result, but these are not critical dead ends for the stated purpose.