Skip to main content
Glama

CalcBright Calculators

Saudi End of Service Calculator

saudi_end_of_service_calculator
Read-onlyIdempotent

SAR 12,000 a month for 7 years earns SAR 54,000 – or SAR 36,000 if you resign.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "saudi_end_of_service_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd date Leave empty to use today's date. (YYYY-MM-DD)2025-12-31
wageNoLast monthly wage Basic salary plus fixed allowances such as housing (as defined in your contract).
startNoStart date (YYYY-MM-DD)2019-01-03
reasonNoHow did employment end?ended

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / end / default
      Previous value: -"2026-10-11"New value: +"2025-12-31"
    • changedInput schema / properties / start / default
      Previous value: -"2019-01-01"New value: +"2019-01-03"
  2. First observed

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 openWorldHint=false, so the safety profile is covered and the description does not contradict it. What the description adds is a concrete outcome pair showing that resignation reduces the benefit from 54,000 to 36,000, which is genuinely useful behavioral context. It does not disclose other material behavior, such as whether dates default to today, whether the calculation follows Saudi Labor Law Article 84 scheme details, or that the result is an estimate.

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 sentence with zero filler and an immediately concrete illustration, which is well front-loaded and easy to scan. It is efficient, though the space is spent on an example rather than on a purpose statement, so brevity comes at the cost of specification.

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 four-parameter calculator with full schema coverage and no output schema, the description supplies an example output magnitude, which partially compensates for the missing return-value documentation. It remains incomplete on jurisdiction confirmation, date-defaulting behavior, and whether figures are statutory or approximate, all of which matter for a legal-benefit calculator.

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%, with clear inline documentation for start, end, wage and the reason enum, so the schema does the heavy lifting and a baseline of 3 applies. The worked example implicitly illustrates the relationship between wage, tenure and the resigned/ended enum value, but adds no format, boundary or defaulting semantics beyond the schema.

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

Purpose3/5

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

The description is a worked example rather than a statement of purpose: it never says explicitly that the tool computes Saudi end-of-service gratuity, leaving the title and tool name to carry that load. It does convey the core behavior implicitly (a wage of 12,000 over 7 years yields 54,000, halved to 36,000 on resignation), so an agent can infer the function, but there is no specific verb-plus-resource sentence and no differentiation from siblings like gcc_gratuity_calculator or uae_gratuity_calculator.

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 when-to-use or when-not-to-use guidance and no mention of alternative calculators offered by the siblings. The only implicit steering is the resignation scenario, which hints that the 'reason' input changes the result, but the agent is left to infer that this is the Saudi-specific jurisdiction tool versus the GCC or UAE gratuity calculators.

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