Skip to main content
Glama

Suomiatlas — Finnish area statistics

History and trends for a Finnish place

get_place_history
Read-only

Time series for one Finnish postal area or municipality, with the direction and size of change computed for each metric so the trend does not have to be eyeballed. Answers questions like "have apartment prices been rising in Espoo?" and "is the population growing?". Defaults to housing sale prices and population. For a postal area it also returns trendMetrics: precomputed 1/5/10-year indicators — population growth, income momentum, aging velocity, family influx, construction, education uplift, and unemployment relative to the national change — which answer "is this area gentrifying / aging / declining?" directly, and whose latest values are free for everyone. Free callers receive only the last 3 years of series, no per-year history on the trend metrics (Pro or an Area Pass adds up to 10 years per metric), and no municipality housing price history — each reported in locked. A short window is NOT evidence of a short trend: if a field is locked, say the full series requires Pro rather than describing the 3-year window as the trend. Series points are index-aligned to years: a null point is a year the source did not publish for this area, and trend is null when fewer than two points have values or the series starts at zero — call that too sparse to read, not flat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoForce a grain.
placeYesPlace name or code, e.g. "Espoo", "Hervanta", "00560"
variablesNoVariable codes to chart (see list_variables). Defaults to housing prices and population.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / place / description
      Previous value: -"Place name or code, e.g. \"Espoo\", \"Töölö\", \"00560\""New value: +"Place name or code, e.g. \"Espoo\", \"Hervanta\", \"00560\""
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With annotations only covering readOnly/openWorld, the description carries substantial extra context: free-tier limits (last 3 years, no per-year history, no municipality housing prices), how each limitation surfaces in `locked`, null-point semantics aligned to `years`, and the null `trend` condition. It also instructs the agent not to misread a locked 3-year window as the trend.

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-loads the purpose, then layers return-shape and tier-behavior detail; every clause carries information. It is dense, but the long sentences are justified by the interpretive warnings that prevent wrong answers.

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?

No output schema exists, yet the description explains the return shape (index-aligned series, `trendMetrics`, `locked`) and the edge cases (sparse series, locked fields). An agent has everything needed to call and interpret it.

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 schema already documents all three parameters (place, kind, variables). The description only restates the default variables (housing prices and population), adding 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?

States a specific verb+resource+scope: 'Time series for one Finnish postal area or municipality' with trend computation. The `trendMetrics` / gentrification framing makes it clearly distinct from snapshot-style siblings like get_place_stats and compare_areas.

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?

Gives concrete example questions ('have apartment prices been rising in Espoo?') and states defaults, which signals when to use it. However, it never names an alternative tool or an explicit when-not-to-use condition relative to get_place_stats or compare_areas.

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