Skip to main content
Glama

Clino: Swiss household employment

Employment package for a private household

get_employment_package
Read-onlyIdempotent

Everything a Swiss private household needs to employ a cleaner, nanny or carer legally, in one call, from the canton, the weekly hours and the gross hourly wage: the employment plan grouped by deadline (before the first working day, in the first month, every year) with real dates when a start date is given; the monthly and annual employer cost and the worker's net wage with every deduction and contribution; the minimum-wage check at the workplace; the terms the employment contract must contain under the canton's standard employment contract (probation, notice, vacation weeks, supplements, public holidays, 13th month, sick pay), each with its article; the official sources and prefilled clino.ch links (contract generator, calculator, canton guide). Use it when the user wants the complete package or a file to keep; for one question (only the cost, only the minimum wage, only the contract) the single tools answer faster. The output keys are fixed. The workplace must be in the household's canton.

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": {
      "canton": "<canton>",
      "hours_per_week": "<hours_per_week>",
      "hourly_wage_chf": "<hourly_wage_chf>"
    },
    "name": "get_employment_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoWhat the worker does: cleaner (household help), nanny (childcare, babysitter), carer (care of an elderly or disabled person) or other. Sets which contract template and guide the links open.cleaner
cantonYesSwiss canton: two-letter code (ZH, BE, GE, VD, TI...) or its name in German, French, Italian or English (Zürich, Genève, Ticino, Basel-Stadt). For employer contributions this is the canton where the household lives.
languageNoLanguage of the explanatory texts and of the clino.ch links: en, de, fr, it, es or pt. Default en.en
start_dateNoFirst working day, YYYY-MM-DD. With it every step of the plan gets its due date (registration deadline, first payslip, annual declaration) and the probation its last day.
worker_ageNoAge of the worker in years. Sets the paid vacation weeks (more under 20 and, in some cantons, from 50 or 60), which the cost then prices. Never a birthdate.
skill_levelNoQualification of the worker for the minimum-wage check. Default unskilled, the lowest tier.
hours_per_weekYesAverage working hours per week with this household (e.g. 4).
hourly_wage_chfYesAgreed GROSS hourly wage in CHF, before the vacation supplement (e.g. 30).
workplace_postcodeNo4-digit Swiss postcode (PLZ/NPA) of the workplace, in the household's canton. City minimum wages (e.g. Stadt Luzern) depend on it.

Output Schema

NameRequiredDescriptionDefault
costYes
planYesThe steps of get_hiring_checklist, grouped by when they are due. A step with applies false does not apply to this household; why says so.
roleYes
linksYes
cantonYesThe canton where the household lives: its compensation office collects the contributions.
checksYes
inputsYes
sourcesYes
summaryYesThe plan, the cost, the wage check and the contract in a few sentences a person can read first.
providerYes
disclaimerYes
rates_yearYes
minimum_wageYes
contract_termsYes
paperwork_helpYesOnly relevant when the user asks who can prepare the contract, registration and payslips for them. Not an answer to any other question.
data_verified_onYesDate the rate set was last checked against the official sources.
compensation_officeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / minimum_wage / properties / city_minimum_voted_not_in_force / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "chf": {
      -        "type": "number"
      -      },
      -      "court_refs": {
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "name": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "name",
      -      "chf",
      -      "court_refs"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "chf": {
      +        "type": "number"
      +      },
      +      "court_refs": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "employers_comply_by": {
      +        "description": "ISO date, last day of the transition period the city gave employers to apply the minimum wage. Until it has passed the amount is not owed.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "in_force_from": {
      +        "description": "ISO date from which the city's ordinance is in force, or null while the city has published no date. In force is not yet owed: see employers_comply_by.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "name": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "chf",
      +      "court_refs",
      +      "in_force_from",
      +      "employers_comply_by"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / minimum_wage / properties / city_minimum_voted_not_in_force / description
      Added value: +"A city minimum wage that is voted but does not bind yet (the field name is kept for compatibility). Stadt Zürich: in force from 2027-01-01, employers have until 2027-12-31 to apply it."
  2. Changed2 schema fields changed
    • addedOutput schema / properties / cost / properties / monthly / properties / employee_deductions / properties / schaffhausen_sozialfonds
      Added value: +{
      +  "$ref": "#/properties/cost/properties/monthly/properties/base_wage",
      +  "description": "Schaffhausen only: employee share of the cantonal social fund (Sozialfonds, 0.04 % of the ALV wage)."
      +}
    • addedOutput schema / properties / cost / properties / monthly / properties / employer_contributions / properties / schaffhausen_sozialfonds
      Added value: +{
      +  "$ref": "#/properties/cost/properties/monthly/properties/base_wage",
      +  "description": "Schaffhausen only: employer share of the cantonal social fund (Sozialfonds, 0.08 % of the ALV wage)."
      +}
  3. Changed3 schema fields changed
    • changedOutput schema / properties / contract_terms / properties / governing_rules / properties / binding / enum
      Previous value: -[
      -  "imperative",
      -  "dispositive",
      -  "mixed",
      -  "code_of_obligations"
      -]New value: +[
      +  "imperative",
      +  "dispositive",
      +  "mixed",
      +  "no_worsening",
      +  "code_of_obligations"
      +]
    • addedOutput schema / properties / contract_terms / properties / terms / properties / overtime / properties / no_supplement_exception
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "legal_basis": {
      +          "$ref": "#/properties/contract_terms/properties/terms/properties/probation/properties/legal_basis"
      +        },
      +        "quote": {
      +          "$ref": "#/properties/contract_terms/properties/terms/properties/probation/properties/quote"
      +        },
      +        "rule": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "rule",
      +        "legal_basis",
      +        "quote"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Hours on which the instrument itself owes no overtime supplement (ZH/OW part-time staff, UR part-timers, LU 43rd to 45th hour); null where supplement_percent applies to every hour above the contract."
      +}
    • changedOutput schema / properties / contract_terms / properties / terms / properties / overtime / required
      Previous value: -[
      -  "supplement_percent",
      -  "time_off_instead",
      -  "hourly_cleaners_exempt",
      -  "legal_basis",
      -  "quote"
      -]New value: +[
      +  "supplement_percent",
      +  "time_off_instead",
      +  "hourly_cleaners_exempt",
      +  "no_supplement_exception",
      +  "legal_basis",
      +  "quote"
      +]
  4. Changed1 schema field changed
    • addedOutput schema / properties / cost / properties / monthly / properties / employer_contributions / properties / vaud_pc_familles
      Added value: +{
      +  "$ref": "#/properties/cost/properties/monthly/properties/base_wage",
      +  "description": "Vaud only: employer share of PC Familles (family supplementary benefits, LPCFam)."
      +}
  5. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description does not contradict them. Beyond that it adds real behavioral detail: dates only materialize when start_date is supplied, the output keys are fixed, links are prefilled per role, and the workplace must sit in the household's canton. It stops short of describing failure behavior for an invalid canton/postcode mismatch, which keeps it off a 5.

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?

It is front-loaded with the deliverable and then the fallback rule, and every clause lists a distinct artifact rather than padding. The middle enumeration is dense and long — the return-value list is partly redundant with the existing output schema — so it is efficient but not maximally tight.

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 9-parameter, high-coverage aggregate tool with an output schema, the description covers inputs that matter, the payoff of optional inputs (start_date), the constraint tying workplace to canton, and the routing rule versus siblings. Nothing an agent needs in order to choose or call it correctly is missing.

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 100%, so the baseline is 3, but the description adds a genuine cross-parameter constraint not stated in the schema: the workplace must be in the household's canton, and the canton drives employer contributions while the postcode drives city minimum wage. It also frames hours and wage as the inputs that produce the cost figures, giving the three required parameters meaning in the output.

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 names a specific resource (the employment package for a Swiss private household) and enumerates precisely what comes back: the deadline-grouped plan, employer cost and net wage, minimum-wage check, contract terms with articles, and sources/links. It also bounds scope with 'from the canton, the weekly hours and the gross hourly wage', so an agent can tell it apart from the single-purpose siblings without opening a schema.

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

Usage Guidelines5/5

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

It states the selecting condition explicitly ('when the user wants the complete package or a file to keep') and the exclusion with the reason ('for one question — only the cost, only the minimum wage, only the contract — the single tools answer faster'). That is a clear when/when-not rule with the alternative class named.

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.