Skip to main content
Glama

Doviandi Cyprus corporate and tax

Calculate Cyprus employer cost and employee deductions on a salary

cyprus_payroll_contributions
Read-only

Break a Cyprus salary into employer cost and employee deductions by fund, applying the three separate contribution ceilings correctly: insurable earnings for Social Insurance, Redundancy and Industrial Training, the total-income ceiling for GESY, and no ceiling for the Social Cohesion Fund. Income tax is not included.

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": {
      "gross_annual_salary": "<gross_annual_salary>"
    },
    "name": "cyprus_payroll_contributions"
  }
}

Input Schema

NameRequiredDescriptionDefault
holiday_fundNoAdd the Holiday Fund, payable where the employer does not run its own scheme.
gross_annual_salaryYesGross annual salary in euro, before any deduction. For example 60000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / gross_annual_salary / description
      Added value: +"Gross annual salary in euro, before any deduction. For example 60000."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and a closed-world scope, so the description doesn't need to restate safety. It adds real behavioral value by disclosing that three distinct ceilings are applied per fund (insurable earnings vs. total income vs. none) and that income tax is out of scope, which prevents misuse of the result.

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?

A single dense sentence that front-loads the core operation and then qualifies it with the ceiling rules and the tax exclusion. No filler, no repetition of the title.

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 two-parameter, read-only calculator with no output schema, the description gives enough — what it computes, how ceilings differ by fund, and what it omits. The per-fund result shape is only implied by 'by fund', a minor remaining gap.

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%, so both parameters (gross_annual_salary, holiday_fund) are already fully documented in the schema. The description adds no parameter-level detail beyond the fund/ceiling framing, so the 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?

States a specific verb and resource ('Break a Cyprus salary into employer cost and employee deductions by fund'), which is unmistakably a payroll-contribution calculator and distinct from the lookup/test siblings. The scope is further pinned down by naming the exact funds involved.

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?

Usage context is clear (given a gross salary, compute employer contributions and employee deductions). It also draws an explicit boundary — 'Income tax is not included' — which tells the agent not to rely on it for net-pay/tax figures, though it names no alternative sibling tool.

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