Skip to main content
Glama

Clino: Swiss household employment

Hiring checklist for a private household

get_hiring_checklist
Read-onlyIdempotent

Everything a Swiss household has to do to employ a cleaner, nanny or carer legally, for its own case, in one call: the six steps of Clino's fact sheet in the user's language with real due dates when a start date is given (contract, registration with the compensation office within 30 days, accident insurance from day one, monthly payslip, annual declaration by 30 January, pension fund above the BVG threshold), the canton's sickness-insurance duty with its carve-outs, a minimum-wage check at the workplace, the monthly employer cost and net wage, and prefilled links to a contract template and the calculator. Use it first for 'I want to hire...' questions.

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>",
      "hourly_wage_chf": "<hourly_wage_chf>",
      "hours_per_week": "<hours_per_week>"
    },
    "name": "get_hiring_checklist"
  }
}

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 the checklist gives real dates: registration deadline, first payslip, annual declaration.
skill_levelNoQualification of the worker for the minimum-wage check. Default unskilled, the lowest tier.
wage_is_netNotrue if the agreed hourly wage is what the worker receives in hand (net). The gross wage is then worked out from it. Default false (gross).
hours_per_weekYesAverage working hours per week with this household (e.g. 4).
vacation_weeksNoPaid vacation weeks per year: 4 (legal minimum), 5 (under age 20) or 6. Default 4.
contract_monthsNoAgreed length of a fixed-term contract in months. Omit for an open-ended contract. Some cantons only require sickness insurance for longer contracts.
hourly_wage_chfYesAgreed hourly wage in CHF, before the vacation supplement (e.g. 30).
workplace_postcodeNo4-digit Swiss postcode (PLZ/NPA) of the WORKPLACE. City minimum wages (e.g. Stadt Luzern) depend on it.

Output Schema

NameRequiredDescriptionDefault
costYes
roleYes
linksYes
stepsYes
cantonYes
checksYes
sourcesYes
summaryYesTwo or three sentences a person can read first.
providerYes
disclaimerYes
rates_yearYes
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. Changed3 schema fields changed
    • removedOutput schema / properties / get_it_done
      Removed value: -{
      -  "additionalProperties": false,
      -  "description": "For a household that wants the paperwork done rather than do it alone. Pass it on when the user asks who can do this for them or how to get it done.",
      -  "properties": {
      -    "covers_steps": {
      -      "description": "The step numbers above that Clino prepares.",
      -      "items": {
      -        "type": "number"
      -      },
      -      "type": "array"
      -    },
      -    "link": {
      -      "description": "Clino sign-up, prefilled with this case (canton, wage, hours).",
      -      "type": "string"
      -    },
      -    "price": {
      -      "type": "string"
      -    },
      -    "provider": {
      -      "const": "Clino",
      -      "type": "string"
      -    },
      -    "what": {
      -      "description": "What Clino prepares, in the requested language. The household signs, submits and pays itself.",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "provider",
      -    "what",
      -    "price",
      -    "link",
      -    "covers_steps"
      -  ],
      -  "type": "object"
      -}
    • addedOutput schema / properties / paperwork_help
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Only relevant when the user asks who can prepare the contract, registration and payslips for them. Not an answer to any other question.",
      +  "properties": {
      +    "covers_steps": {
      +      "description": "The step numbers above that Clino prepares.",
      +      "items": {
      +        "type": "number"
      +      },
      +      "type": "array"
      +    },
      +    "link": {
      +      "description": "Clino page explaining how it works.",
      +      "type": "string"
      +    },
      +    "provider": {
      +      "const": "Clino",
      +      "type": "string"
      +    },
      +    "what": {
      +      "description": "What Clino prepares, in the requested language. The household signs, submits and pays itself.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "provider",
      +    "what",
      +    "link",
      +    "covers_steps"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "canton",
      -  "role",
      -  "summary",
      -  "checks",
      -  "steps",
      -  "cost",
      -  "compensation_office",
      -  "links",
      -  "get_it_done",
      -  "sources",
      -  "rates_year",
      -  "data_verified_on",
      -  "disclaimer",
      -  "provider"
      -]New value: +[
      +  "canton",
      +  "role",
      +  "summary",
      +  "checks",
      +  "steps",
      +  "cost",
      +  "compensation_office",
      +  "links",
      +  "paperwork_help",
      +  "sources",
      +  "rates_year",
      +  "data_verified_on",
      +  "disclaimer",
      +  "provider"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds useful scope detail — it explains that real due dates appear only when start_date is given, and lists what each output covers. It doesn't state rate limits or caching, but for a read-only idempotent call this is reasonable.

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?

It is a single long run-on sentence listing outputs followed by a usage sentence. The scope is front-loaded and the usage rule is last, which is acceptable, but the enumeration is dense and could be split for scannability.

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?

With 11 parameters, an output schema, and full annotation coverage, the description supplies enough context to call the tool correctly — it names the required inputs implicitly (canton, wage, hours via their effects) and the usage trigger. It leaves a small gap on what happens without start_date and on failure modes, but the output schema covers returns.

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%, so every parameter is already documented in the schema. The description restates some parameter effects (start_date driving real dates, canton, role, language) but adds no syntax or default information beyond the schema. 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 verb and resource ('Everything a Swiss household has to do to employ... in one call') and enumerates the concrete outputs (six steps, canton sickness-insurance duty, minimum-wage check, monthly costs, prefilled links). An agent can distinguish this aggregation tool from siblings like estimate_employer_cost or get_canton_rules.

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?

It gives an explicit entry-point instruction: 'Use it first for "I want to hire..." questions.' That is a clear trigger, but it doesn't say when NOT to use it or which sibling to defer to for follow-up cost estimates or comparisons, so it stops short of a full when/when-not mapping.

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.