Skip to main content
Glama

Leave entitlements, notice and severance

leave_and_termination
Read-only

Returns BCEA minimum leave (annual, sick, family responsibility), notice period and retrenchment severance pay for an employee, given days worked per week, start date and pay.

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": {
      "days_per_week": "<days_per_week>",
      "start_date": "<start_date>"
    },
    "name": "leave_and_termination"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_atNoDate to evaluate, default today
start_dateYesEmployment start, YYYY-MM-DD
weekly_wageNoOrdinary weekly wage in rand (for severance)
worker_typeNoSector: general, farm or domestic (farm and domestic workers have longer notice periods). Default generalgeneral
days_per_weekYesDays worked per week, e.g. 5 or 6

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / worker_type / description
      Added value: +"Sector: general, farm or domestic (farm and domestic workers have longer notice periods). Default general"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds meaningful context by grounding results in statutory BCEA minimums (not company policy) and naming the three output components, but it leaves the return format, units (days vs weeks vs rand), rounding, and what happens when weekly_wage is omitted undocumented — notable since no output schema exists.

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 names the outputs first and the driving inputs second, with no filler. It is dense but every clause carries information; it stops just short of ideal because the parenthetical leave breakdown could be trimmed or the space used for unit/format details.

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

Completeness3/5

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

For a 5-parameter, read-only statutory calculation with no output schema, the description covers purpose and output components but not result shape, units, or the effect of the optional as_at and weekly_wage parameters. Adequate to invoke, but an agent would still be guessing about the response structure.

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% including a documented enum for worker_type, so the schema carries the parameter burden and baseline 3 applies. The description adds only mild linkage value by naming the inputs ('days worked per week, start date and pay') and implying pay feeds severance, without specifying role of as_at or edge-case handling for missing pay.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Returns') and the concrete resources computed: BCEA minimum leave (annual, sick, family responsibility), notice period, and retrenchment severance pay. This is clearly distinct from every sibling (minimum_wage_check, overtime_and_premium_pay, public_holidays, uif_sdl_contributions), so an agent can route to it without inspecting schemas.

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?

Usage is implied rather than stated: it is 'for an employee' and requires days worked per week and a start date, which hints at a per-employee entitlement calculation. There is no explicit when-to-use/when-not guidance, no mention of prerequisites (e.g. that weekly_wage is only needed for severance), and no routing against the sibling tools.

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.

Resources