Skip to main content
Glama

Holiday Roster Payroll

bpj_holiday_roster_payroll
Read-onlyIdempotent

Budget gross payroll for holiday opening using staffed shifts, paid hours and the supplied premium above base wages.

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": {
      "holiday": "<holiday>",
      "shifts": "<shifts>",
      "posts": "<posts>",
      "shiftLength": "<shiftLength>",
      "rate": "<rate>",
      "holidayExtra": "<holidayExtra>"
    },
    "name": "bpj_holiday_roster_payroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYes
postsYes
shiftsYes
holidayYes
shiftLengthYes
holidayExtraYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/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 the safety profile is covered. The description adds that this is a pure budgeting computation over supplied inputs, which is useful. However, it does not disclose the calculation's mechanics — whether the premium applies to all paid hours or only holiday days — nor the unit and rounding of the result.

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 tightly packed sentence with no filler and the core purpose front-loaded. It is efficient, though the compression ('budget gross payroll') trades some clarity for brevity.

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?

This is a six-parameter required-input calculator with no output schema, so the description is the only place an agent can learn what comes back. It does not say whether the result is a single gross total or a breakdown, what currency or rounding applies, or how the premium is applied across days and posts — significant gaps for a computation tool.

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 0%, so the description must carry parameter meaning, and it partially does: 'staffed shifts' maps to shifts and posts, 'paid hours' clarifies shiftLength, and 'premium above base wages' maps to holidayExtra and rate. It leaves the premium's percentage basis ambiguous (only the schema title reveals it is a percent) and never addresses holiday operating days, so a full 3 rather than a 4.

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 specific action and resource: computing gross payroll for a holiday opening from shifts, paid hours and a premium above base wages. An agent can immediately tell this is a payroll cost estimator rather than a scheduler or an absence-cost tool. It stops short of naming or contrasting any sibling, so differentiation is inferred rather than stated.

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 'for holiday opening' implies the scenario in which it applies, and the inputs listed imply it is a forward-looking budgeting calculation. There is no explicit when-to-use versus when-not guidance, no mention of alternatives, and no stated prerequisites such as whether it substitutes for or complements an actual-cost tool.

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.