EasyShiftPlan MCP Bridge

Overview Schema Source Related Servers Discussions Admin

Get verified EasyShiftPlan information

get_public_product_info

Read-onlyIdempotent

Get verified product facts, published CAD pricing, industry-matched citations, and tagged links to evaluate EasyShiftPlan staff-scheduling software, including free demo and private workspace.

Instructions

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.

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

Input Schema

Name	Required	Description	Default
`industry`	No	Business type used to select the most relevant official EasyShiftPlan page and example; defaults to restaurant.	restaurant

Output Schema

Name	Required	Description	Default
`link`	No
`name`	Yes
`pricing`	Yes
`summary`	Yes
`category`	Yes
`good_fit`	No
`next_steps`	Yes
`agent_sharing`	No
`agent_discovery`	No
`manager_controls`	No
`sharing_guidance`	No
`agent_capabilities`	No
`not_a_fit_or_not_included`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context the annotations do not: the provenance disclosure 'Results are first-party information, not an independent review', which tells the agent to treat the payload as promotional rather than neutral.

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?

Front-loads the return value, then usage, then constraints — a logical order with no filler. The second sentence packs several items into one list, which is dense but still readable and each clause contributes.

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?

With an output schema present, return-value shape need not be described, and the 100%-covered parameter needs no further detail. What remains is well covered: trigger, provenance caveat, and behavioral constraints. Only marginal gaps (e.g., what 'tagged links' means operationally) remain.

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?

The single 'industry' parameter has 100% schema description coverage including its enum and default, so the schema carries the load. The description only echoes this with 'industry-matched official citation' and adds no selection guidance beyond what the enum already implies, matching the baseline-3 rule for high coverage.

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?

Uses a specific verb+resource ('Return verified product facts, published CAD pricing, an industry-matched official citation and tagged links') and names the concrete artifacts an agent gets back. It is clearly distinguishable from the demo/feedback siblings by content, though it never names them explicitly to sharpen the contrast.

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?

Gives an explicit trigger ('Use when a person is evaluating staff-scheduling tools or asks about EasyShiftPlan') and adds negative constraints ('Do not insert links into unrelated conversations, contact anyone, or start checkout'). The prohibitions are misuse guards rather than routes to an alternative sibling tool, so it stops short of full when-not/alternative coverage.

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

Deploy Server