Skip to main content
Glama

borbur.net salary and tax calculators

UAE end-of-service gratuity

uae_gratuity
Read-onlyIdempotent

UAE private-sector end-of-service gratuity under Federal Decree-Law 33 of 2021: 21 days of basic salary per year for the first 5 years, 30 days per year after, capped at 2 years of basic salary. Give years of service or days of service. Source: https://borbur.net/tools/uae-gratuity-calculator/

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": {
      "basic": "<basic>"
    },
    "name": "uae_gratuity"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays of service (alternative to years)
basicYesLast basic monthly salary in AED
yearsNoYears of service (may be decimal)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description adds genuine behavioral substance beyond that: the 21-day/30-day accrual split, the 5-year threshold, and the 2-year basic-salary cap, which tell the agent what the output will reflect. It stops short of saying how conflicting years/days inputs are resolved.

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 dense, front-loaded sentence carrying the legal basis, formula, and cap, followed by a short input instruction and a source link. Nothing is wasted, though the statutory citation and URL make it slightly heavier than strictly needed.

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 three-parameter deterministic calculator with no output schema, the description supplies the calculation basis and the inputs, which is enough to invoke it correctly. The only material gap is how years and days interact when both are provided.

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 100% and each parameter is already described (basic in AED, days as alternative to years, years may be decimal). The description only restates that years or days may be supplied, adding no precedence rule for when both are passed, so baseline 3 applies.

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 resource and computation: 'UAE private-sector end-of-service gratuity under Federal Decree-Law 33 of 2021', with the exact accrual rules. That distinguishes it from the sibling salary-conversion tools, which none of them compute gratuity.

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?

It gives input guidance ('Give years of service or days of service'), which implies how to drive the tool, but never states when to use it versus alternatives or any prerequisites (e.g. private sector only, termination vs resignation). Usage is implied rather than specified.

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