Skip to main content
Glama

Check pay against the national minimum wage

minimum_wage_check
Read-only

Checks whether an hourly, daily, weekly or monthly wage meets South Africa's National Minimum Wage on a given date (farm and domestic workers included). Returns the legal minimum, the shortfall and monthly equivalents.

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": {
      "amount": "<amount>",
      "period": "<period>"
    },
    "name": "minimum_wage_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD, default today
amountYesWage in rand
periodYesWhat the amount covers: per hour, day, week or month
worker_typeNoSector: general, farm, domestic, or epwp (Expanded Public Works Programme, which has its own lower minimum). Default generalgeneral
hours_per_dayNoOrdinary hours per day (needed for day). Default 9
hours_per_weekNoOrdinary hours per week (needed for week/month). Default 45

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / period / description
      Added value: +"What the amount covers: per hour, day, week or month"
    • addedInput schema / properties / worker_type / description
      Added value: +"Sector: general, farm, domestic, or epwp (Expanded Public Works Programme, which has its own lower minimum). Default general"
  2. First observed

TDQS

A3.8/5.0
Behavior4/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 genuine context beyond that: it is date-sensitive, covers farm and domestic workers, and returns the legal minimum, the shortfall and monthly equivalents, which tells the agent what a result looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two front-loaded sentences: the check and its scope first, the return payload second. No filler, no repetition of the title verbatim.

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

Completeness4/5

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

For a 6-parameter, no-output-schema calculation tool, the description covers the domain, date sensitivity and expected outputs adequately. Minor gap: it doesn't mention the epwp sector or how hours_per_day/hours_per_week affect conversions, leaving the agent to rely on the schema.

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%, so every parameter including the epwp sector and hours defaults is already documented in the schema. The description restates period options and the farm/domestic inclusion but adds no syntax or edge-case meaning beyond that; baseline 3 applies.

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 verb (checks) and resource (wage vs. South Africa's National Minimum Wage) with jurisdiction, period granularity and worker coverage spelled out. It is clearly distinguishable from siblings like overtime_and_premium_pay or uif_sdl_contributions, though it never explicitly names them.

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 by the purpose: use it to test a pay figure against the legal floor on a date. There is no explicit when-to-use/when-not guidance and no routing to related siblings (e.g. overtime or leave tools) for adjacent questions.

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