Skip to main content
Glama

Night Shift Differential

bpj_night_shift_differential
Read-onlyIdempotent

Add a fixed differential for night hours and compute the effective pay rate across all paid hours.

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": {
      "actual": "<actual>",
      "night": "<night>",
      "rate": "<rate>",
      "premium": "<premium>"
    },
    "name": "bpj_night_shift_differential"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYes
nightYes
actualYes
premiumYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the differential is fixed and applied across all paid hours, but it never discloses the actual formula or how premium, night hours, and actual hours combine, and there is no output schema to compensate.

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. It is efficient, though its brevity is part of why the formula and parameter roles go unexplained.

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?

For a four-required-parameter calculation with no output schema, the agent needs the relationship between inputs to predict the result, and this is absent. The description is under-specified relative to the complexity of the computation.

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 parameter meaning, and it names none of the four parameters. The schema's own titles ('Base hourly rate', 'Night-shift hours', 'Paid hours this week', 'Extra allowance per night hour') do most of the work, but the critical question of how they interact is left unstated.

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 states a specific computation: applying a night-hours differential and deriving an effective pay rate across all paid hours. That is enough for an agent to distinguish this payroll calculation from unrelated siblings. It loses a point because 'Add a fixed differential' is slightly ambiguous about whether anything is written or merely computed.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool, what preconditions apply (e.g. weekly hour caps), or what alternative to reach for. The agent must infer entirely from the parameter list that this is a payroll effective-rate calculation.

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.