Skip to main content
Glama

PoliErgaleio

calculate_cyprus_state_pension

Estimates the Cyprus state (contributory) pension amount at retirement using official contribution schedules and current 2026 pension income-tax bands, based on accumulated insurance units and contribution history. Use to estimate contributory Cyprus state pension entitlement and amount at retirement. Results apply the current 2026 pension income-tax bands; projected contribution amounts use the published SI rate increases in 2029, 2034 and 2039. Reuse supplied facts and ask only for missing essentials: mode and retirement age are always required; quick mode also needs current age, years worked and total insurance units; advanced mode needs the actual non-empty yearly contribution record. Ask for dependants or state the zero-dependants assumption before presenting a personalized result. Never infer contribution history or eligibility facts. Missing insurance-statement facts leave qualifiesForPension null and a conditional amount estimate; special/cross-border routes require assessment. Units are per calendar year; a legacy year-to-units map is accepted.

Input Schema

NameRequiredDescriptionDefault
modeYesCalculation mode.
currentAgeNoCurrent age (quick mode only).
dependentsNoLegacy estimated dependant count. It cannot identify an eligible spouse; use dependentSpouse and otherDependents for the statutory tier.
yearlyUnitsNoAdvanced mode only. Insurance units earned per calendar year, e.g. [{"year":2003,"units":5.2}]. Units per year must be between 0 and the statutory maximum for that year (about 5.3-6.0; 6.0 for years after 2026). A legacy object map {"2003": 5.2} is also accepted. Years worked and total units are derived from this array, so yearsWorked/totalInsuranceUnits are ignored in advanced mode.
yearsWorkedNoActual years with insurance contributions (quick mode); do not infer from age or employment duration.
retirementAgeYesPlanned retirement age.
dependentSpouseNoConfirmed eligibility for a dependent-spouse pension increase; not merely married.
otherDependentsNoOther confirmed eligible dependants; increase is capped at two. Supply with dependentSpouse for an exact dependant tier.
eligibilityFactsNo
totalInsuranceUnitsNoActual accumulated Cyprus insurance units/points (quick mode); do not infer from salary or years worked.

Output Schema

NameRequiredDescriptionDefault
seriesNo
incomeTaxYes
monthlyNetYes
totalUnitsYes
assumptionsYes
eligibilityYes
weeklyGrossYes
yearsWorkedYes
ghsDeductionYes
estimateAssumptionsYes
qualifiesForPensionYes
basicPensionComponentYes
minimumPensionAppliedYes
estimatedAnnualPensionYes
estimatedMonthlyPensionYes
earningsRelatedComponentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / dependentSpouse
      Added value: +{
      +  "description": "Confirmed eligibility for a dependent-spouse pension increase; not merely married.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / dependents / description
      Previous value: -"Number of dependents (spouse/children); raises the basic pension multiplier."New value: +"Legacy estimated dependant count. It cannot identify an eligible spouse; use dependentSpouse and otherDependents for the statutory tier."
    • addedInput schema / properties / eligibilityFacts
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "actualBasicInsurancePoints": {
      +      "description": "Actual paid basic insurance points at claim date; credited points do not satisfy the actual-points condition.",
      +      "minimum": 0,
      +      "type": "number"
      +    },
      +    "referencePeriodYears": {
      +      "description": "Reference period from the insurance statement, including applicable statutory exclusions.",
      +      "exclusiveMinimum": 0,
      +      "maximum": 70,
      +      "type": "number"
      +    },
      +    "standardDomesticCase": {
      +      "description": "Confirm the ordinary domestic route, without special invalidity, miner or cross-border provisions. False or omitted leaves eligibility undetermined.",
      +      "type": "boolean"
      +    },
      +    "totalBasicInsurancePoints": {
      +      "description": "Paid plus credited BASIC points, not total basic-plus-supplementary insurance units.",
      +      "minimum": 0,
      +      "type": "number"
      +    },
      +    "weeksSinceFirstInsurance": {
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / otherDependents
      Added value: +{
      +  "description": "Other confirmed eligible dependants; increase is capped at two. Supply with dependentSpouse for an exact dependant tier.",
      +  "maximum": 10,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / eligibility
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "reasons": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "status": {
      +      "enum": [
      +        "eligible",
      +        "ineligible",
      +        "undetermined"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "reasons"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / estimateAssumptions
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / qualifiesForPension / type
      Previous value: -"boolean"New value: +[
      +  "boolean",
      +  "null"
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "estimatedMonthlyPension",
      -  "estimatedAnnualPension",
      -  "basicPensionComponent",
      -  "earningsRelatedComponent",
      -  "minimumPensionApplied",
      -  "qualifiesForPension",
      -  "monthlyNet",
      -  "weeklyGross",
      -  "ghsDeduction",
      -  "incomeTax",
      -  "yearsWorked",
      -  "totalUnits",
      -  "assumptions"
      -]New value: +[
      +  "estimatedMonthlyPension",
      +  "estimatedAnnualPension",
      +  "basicPensionComponent",
      +  "earningsRelatedComponent",
      +  "minimumPensionApplied",
      +  "qualifiesForPension",
      +  "eligibility",
      +  "estimateAssumptions",
      +  "monthlyNet",
      +  "weeklyGross",
      +  "ghsDeduction",
      +  "incomeTax",
      +  "yearsWorked",
      +  "totalUnits",
      +  "assumptions"
      +]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the tax-year basis (2026 bands), projection assumptions (published SI rate increases in 2029, 2034, 2039), and edge-case output behaviour (missing insurance-statement facts leave qualifiesForPension null with only a conditional amount estimate; special/cross-border routes require assessment). It also flags an accepted legacy input form, so an agent knows which surface it is dealing with.

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

Conciseness3/5

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

The purpose is front-loaded, but the second sentence ('Use to estimate contributory Cyprus state pension entitlement and amount at retirement') largely repeats the first. The remainder is a dense run-on chain of clauses with no grouping, mixing required-parameter rules, assumption handling, null semantics and input-format notes, which costs scanability.

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

Completeness5/5

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

For a 10-parameter, nested-object calculator with no annotations, the description covers what an agent needs: the two modes and their required inputs, the projection/time basis of the numbers, the assumption it must confirm before personalising, and what the result means when facts are missing. Return-value detail is legitimately delegated to the existing output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 90%, so the baseline is 3; the description adds real meaning on top by restating the mode-conditional requirement sets in prose and telling the agent what must not be inferred (contribution history, eligibility facts, units from salary). The dependant-tier steering toward dependentSpouse/otherDependents adds a little more. Minor duplication with the schema's allOf conditions keeps it at 4 rather than 5.

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?

States a specific verb and resource — 'Estimates the Cyprus state (contributory) pension amount at retirement' — with the method (official contribution schedules, 2026 tax bands, insurance units). That scope is specific enough to distinguish it from the neighbouring calculate_cyprus_income_tax, calculate_cyprus_unemployment_benefit and parse_pension_statement tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit mode-level usage rules (mode and retirementAge always required; quick needs currentAge/yearsWorked/totalInsuranceUnits; advanced needs the non-empty yearly record) plus procedural guidance: ask for dependants or state the zero-dependants assumption, never infer contribution history or eligibility facts. It stops short of naming alternatives or exclusions — e.g. when to first call parse_pension_statement or get_pension_reference_data — which keeps it below a 5.

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