Skip to main content
Glama

swiss-living-index

Cantonal minimum wages

get_minimum_wage
Read-onlyIdempotent

Statutory cantonal minimum wages in Switzerland (official cantonal pages): hourly amount, valid from, history and the monthly equivalent at 40 hours. Only five cantons have one (BS, GE, JU, NE, TI); without canton the list of all five is returned. Elsewhere minimums apply only through collective or standard employment contracts.

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": "get_minimum_wage"
  }
}

Input Schema

NameRequiredDescriptionDefault
cantonNoCanton as 2-letter abbreviation, e.g. "ZH", "GE", "TI". Only BS, GE, JU, NE and TI have one; omit for all five.

Output Schema

NameRequiredDescriptionDefault
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / canton / description
      Added value: +"Canton as 2-letter abbreviation, e.g. \"ZH\", \"GE\", \"TI\". Only BS, GE, JU, NE and TI have one; omit for all five."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "attribution": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the bar is lower; the description adds genuinely useful context beyond them: the default behavior when canton is omitted, the hard coverage limit of five cantons, and the 40-hour basis for the monthly figure. It does not describe error behavior for unsupported cantons, but the coverage caveat largely pre-empts that.

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?

Three dense sentences, front-loaded with the resource and scope, then the canton caveat, then the legal-context note. The only mild redundancy is restating the five-canton restriction that also appears in the schema, but each sentence still carries distinct information.

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 single optional parameter tool with an output schema, the description supplies everything an agent needs: what is returned, the geographic applicability limit, and the default branch. Return-value details can be left to the output schema, so nothing material is missing.

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% and the single canton parameter already documents the 2-letter format, the valid canton list, and the omit-for-all behavior. The description restates the five-canton constraint and the omit case but adds no format or syntax detail beyond the schema, 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?

The description names a specific resource (statutory cantonal minimum wages in Switzerland) and enumerates exactly what is returned: hourly amount, valid-from date, history, and the monthly equivalent at 40 hours. It also bounds the scope to five named cantons, so an agent can immediately tell this apart from wage-related siblings like get_salary or salary_by_occupation.

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 states clear usage conditions: omit canton to get all five, and elsewhere minimums only exist via collective/standard employment contracts, which tells the agent the tool is inapplicable outside those cantons. It stops short of explicitly naming an alternative sibling for non-cantonal wage questions, so it falls just short of 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