Stratum Shifts

Get workplace

get_workplace

Read-onlyIdempotent

Use this when you need the current team and rules before scheduling: workplaces, staff (roles, availability, hour limits, time off), the shifts each day needs, and the plan limits. Read-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": "get_workplace"
  }
}

Input Schema

Name	Required	Description	Default
`workplace_id`	No	Workplace id. Omit to use the first workplace.
`include_staff_links`	No	Also list each person's own link (their schedule, a calendar that updates itself, and time-off requests), for the manager to send to each person privately.

Output Schema

Name	Required	Description
`plan`	No
`staff`	No
`current`	Yes
`requests`	No	Time-off requests from staff waiting for an answer
`signedIn`	No
`teamLink`	No	The link that always opens the newest published week
`staffLinks`	No	Each person's own link, present when asked for; send each only to that person
`workplaces`	Yes
`shiftsNeeded`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so 'Read-only.' adds nothing new. The description's enumeration of returned data has some value, but an output schema exists that already defines the response, leaving only modest additive context.

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?

A single front-loaded sentence that leads with the when-to-use condition and then packs the content list, with no filler. The trailing 'Read-only.' is redundant against readOnlyHint but costs little.

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?

For a zero-required-parameter read tool with full schema coverage and an output schema, the description covers the essential purpose and timing. Only the relative positioning against sibling read tools is left implicit.

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% and both parameters are well documented there, including the 'omit to use the first workplace' default and the meaning of include_staff_links. The description adds no parameter-level detail, so the baseline 3 applies.

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?

States a concrete verb+resource ('get_workplace') and enumerates exactly what it returns: workplaces, staff with roles/availability/hour limits/time off, required shifts, and plan limits. The 'before scheduling' framing implicitly separates it from schedule-viewing siblings like show_week, but no sibling is named explicitly.

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?

'Use this when you need the current team and rules before scheduling' gives a clear triggering context tied to the scheduling workflow. It stops short of explicit exclusions or naming alternatives (e.g. show_week, set_up_workplace), so an agent must infer the boundaries.

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

All Stratum Shifts 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?