Skip to main content
Glama

Unused Leave Payout Liability

bpj_leave_payout_liability
Read-onlyIdempotent

Value payable accrued leave at an average hourly wage and add the specified employer on-cost.

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": {
      "unused": "<unused>",
      "rate": "<rate>",
      "burden": "<burden>"
    },
    "name": "bpj_leave_payout_liability"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYes
burdenYes
unusedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 closed-world, so the safety profile is covered. The description adds the key behavioral fact that the on-cost is applied on top of the wage-valued leave, but says nothing about rounding, currency assumptions, or output shape. Adequate but thin beyond the annotations.

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?

One tight sentence, front-loaded with the operation and ending with the on-cost modifier. No filler, though it packs two operations into one clause with minimal structural signposting.

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?

A calculation tool with three required, fully undocumented parameters and no output schema; the description never states what the result represents (total liability, per-period, currency) or how the three inputs combine arithmetically. For a numeric calculator, that leaves the agent guessing at the return value.

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 coverage is 0%, so the description must compensate, and it partially does: it establishes that "rate" is an hourly wage, "unused" is hours of leave, and "burden" is an employer on-cost percentage applied on top. It adds no guidance on units, whether burden is a percentage vs multiplier beyond the title, or expected magnitude/allowed ranges.

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?

Specific verb phrase ("value payable accrued leave at an average hourly wage") plus the added employer on-cost makes the computation clear and distinct from siblings like bpj_absence_cover_cost or bpj_capped_leave_accrual. It does not explicitly name a sibling to disambiguate against, so it stops short of 5.

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?

No when-to-use guidance, no preconditions, no mention of alternatives such as accrual or absence-cost tools. The agent must infer the scenario (termination/liability reporting) entirely on its own.

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.