Skip to main content
Glama

get_population

Read-onlyIdempotent

Retrieve permanent resident population statistics for Switzerland, a specific canton, or all cantons, with optional year selection from 2010 onward.

Instructions

Permanent resident population (BFS STATPOP) for Switzerland, a canton or all cantons

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_population"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoSTATPOP year, from 2010; default is the latest published
cantonNoCanton code or name (e.g. ZH, Geneva); 'all' for every canton; omit for national total

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • changedInput schema / properties / canton / description
      Previous value: -"Canton name or 2-letter code (e.g. 'ZH', 'Zürich', 'Geneva', 'BE'). Omit to get Switzerland total. Use 'all' to list all cantons."New value: +"Canton code or name (e.g. ZH, Geneva); 'all' for every canton; omit for national total"
    • changedInput schema / properties / year / description
      Previous value: -"Year of data (2010–2024). Defaults to latest (2024)."New value: +"STATPOP year, from 2010; default is the latest published"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds the useful provenance detail (BFS STATPOP) but says nothing about freshness, whether the default year can lag actual publication, or the response shape. Given the annotation coverage, a 3 is appropriate.

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?

One short, front-loaded fragment with no filler; the resource and its source lead, and the geographic scope follows. It is slightly clipped (no verb, reads as a label rather than a statement of what the tool does), which keeps it from a 5.

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?

This is a simple zero-required-parameter read tool with a fully described schema and no output schema, so the description need not explain return values. It covers source and scope adequately; only the absence of any routing to the generic statistics tools leaves a small 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 description coverage is 100%, with both parameters documented including the 2010 lower bound, the default-to-latest behavior, and accepted canton formats ('all', code, or name). The description reinforces the scope dimension but adds no syntax or format detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (permanent resident population) and its authoritative source (BFS STATPOP), and states the geographic resolution (Switzerland, a canton, or all cantons). It is clear what data comes back, though it never explicitly says the tool 'returns' population figures and does not distinguish itself from generic siblings like get_statistic or search_statistics.

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: the mention of national, single-canton and all-canton scopes hints at the three ways to call it, but there is no explicit when-to-use guidance and no pointer away from the generic statistics tools (search_statistics, get_statistic) that could also surface population data. An agent has to infer the choice itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools