Skip to main content
Glama

swiss-living-index

Swiss permit types

permit_types
Read-onlyIdempotent

Swiss residence permits L, B, C, Ci, G, F, N, S (incl. the asylum statuses): what each permit is, the official rules (validity, renewal, C permit after 10 or 5 years, language levels, EU/EFTA 5-year list, moving within Switzerland) each with its law article (AIG, VZAE, BüG) or SEM page, and the number of people per permit (BFS, 2010 to latest year) for Switzerland or a canton. Information, not legal advice: the cantonal migration office decides.

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

Input Schema

NameRequiredDescriptionDefault
cantonNooptional canton, e.g. ZH
historyNoinclude all years, default false

Output Schema

NameRequiredDescriptionDefault
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "attribution": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations cover safety (readOnly, idempotent, non-destructive), so the description's job is to add operational context, which it does: it discloses data provenance (AIG/VZAE/BüG articles, SEM pages, BFS statistics), temporal coverage (2010 to latest year), and the important caveat that it is informational and the cantonal migration office decides. It does not discuss granularity limits or how missing permits are handled.

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?

Front-loaded with the permit list, then rules, then statistics, then the disclaimer. It is dense and long but almost every clause carries information; only the nested parenthetical lists make it slightly hard to scan.

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 two-optional-parameter, read-only reference tool with an output schema and full annotation coverage, the description supplies scope (permits + rules + statistics), sourcing, time range, and the legal disclaimer. Nothing an agent needs to call it correctly 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%, so the schema already explains both parameters; the description only adds that the canton form is 'for Switzerland or a canton' and that statistics run from 2010 to latest, marginally reinforcing the history flag. Baseline 3 is appropriate.

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 resource (Swiss residence permits L, B, C, Ci, G, F, N, S) and concretely what it returns: rule descriptions with law articles and per-permit population counts. An agent can tell it apart from siblings like which_permit or naturalisation_canton_rules without opening the schema.

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

Usage Guidelines3/5

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

Usage is only implied by content: it's clearly the reference/explainer endpoint, contrasted implicitly with the decision-oriented which_permit sibling. No explicit when-to-use/when-not-to-use statement or named alternative, even though which_permit and immigration_reasons are obvious overlaps an agent must disambiguate.

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