Skip to main content
Glama

Weekly Shift Post Coverage

bpj_weekly_shift_post_coverage
Read-onlyIdempotent

Estimate a lower bound on roster size from weekly post-shifts and shifts available per employee, before rest-day constraints.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "openDays": "<openDays>",
      "shifts": "<shifts>",
      "posts": "<posts>",
      "cover": "<cover>"
    },
    "name": "bpj_weekly_shift_post_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
coverYes
postsYes
shiftsYes
openDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real semantic context beyond them: the result is a LOWER BOUND and deliberately excludes rest-day constraints, which tells the agent the output under-estimates true staffing need. It does not state rounding behavior or total absence of side effects beyond what annotations cover.

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 with no filler; the qualifier about rest-day constraints is placed at the end where it reads naturally. It is dense rather than padded, though the density costs some readability.

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

Completeness2/5

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

There is no output schema, so the description should say what comes back (headcount integer, rounding direction) and it does not. For a four-required-parameter calculation tool where the exact formula determines correctness, the definition leaves too much to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden, and it only touches two of the four inputs ('post-shifts', 'shifts available per employee'). 'openDays' is never addressed, and the arithmetic relationship among openDays × shifts × posts ÷ cover is left entirely for the agent to infer.

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?

The description uses a specific verb+resource ('Estimate a lower bound on roster size') and names the determining inputs, so an agent knows it computes a headcount figure rather than scheduling shifts. Sibling tools in this catalog are unrelated utility functions, so no differentiation is required. The jargon 'post-shifts' is slightly opaque but recoverable from the schema titles.

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

Usage Guidelines3/5

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

The phrase 'before rest-day constraints' implies this is a pre-scheduling sanity check whose result is a floor, not a final answer, which is genuine usage context. However, there is no explicit when-to-use/when-not statement and no named alternative for a full roster computation with rest-day rules.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.