Suomiatlas — Finnish area statistics

Statistics for a Finnish place

get_place_stats

Current statistics for one Finnish postal area or municipality: population, age, income, employment, education, housing sale prices (€/m²) and municipal crime rates, with national/regional percentiles where available. Accepts a name or a code and resolves it automatically; if the name is ambiguous it returns the candidates instead of guessing. Answers questions like "how many people live in Toukola?", "how many live in Akaa?" and "how much is an apartment in Töölö?". Returns a headline set of metrics by default — pass variables to fetch specific codes from list_variables. A postal area's result also includes ratios[]: household composition and jobs-to-residents ratios compared against Finland as a whole (see each entry's nationalBasis and the response's notes). Anything in the locked field is withheld pending a Pro subscription, not missing: say so rather than reporting it as absent.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No	Force a grain when a name exists at both, e.g. Helsinki the municipality.
`year`	No	Statistics year; defaults to the newest available.
`place`	Yes	Place name or code, e.g. "Toukola", "Akaa", "00560"
`variables`	No	Extra variable codes to include beyond the headline set (see list_variables).
`includeAllVariables`	No	Return all ~131 variables. Large; only use when the headline set is insufficient.
`includeCompositeScores`	No	Include composite 0-100 scores (postal areas only). Component detail needs Pro.

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations provided, the description carries full transparency burden. It discloses automatic resolution, returning candidates on ambiguity, default headline metrics, postal-area ratios, and the crucial `locked`-field Pro subscription caveat. This goes well beyond a basic purpose statement and is exceptionally transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core function, followed by resolution behavior, illustrative examples, default metrics, special postal-area data, and locked-field handling. Every sentence provides distinct value, and the length is appropriate for the tool's complexity.

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?

Given no output schema and no annotations, the description equips the agent with all necessary context: what metrics are returned, how ambiguity is handled, how to request specific variables, the structure of ratios data, and the meaning of `locked`. It is remarkably complete for a tool of this complexity.

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?

The input schema already has thorough descriptions for all six parameters (100% coverage), including defaults, enums, and usage warnings. The description only repeats what the schema states (e.g., accepting name/code, passing variables), adding no new semantic value. Baseline of 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?

The description clearly identifies the tool as returning current statistics for a single Finnish place, enumerates specific metric categories (population, income, housing prices, crime rates), and provides concrete example questions. It distinguishes itself from sibling comparison/ranking tools by focusing on one place's statistics.

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?

The description gives solid usage guidance: automatic name/code resolution with ambiguity handling, using the `variables` parameter for specific codes via list_variables, and how to handle `locked` fields. It does not explicitly mention when to avoid this tool or name alternative tools, so it falls 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.

All Suomiatlas — Finnish area statistics tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool targets a unique operation: comparison, similarity, air quality, report download, history, current stats, variable listing, ranking, and place resolution. There is no functional overlap, and the descriptions reinforce distinct purposes.

Naming Consistency5/5

All tools use consistent verb_noun naming: compare_areas, find_similar_areas, get_air_quality, get_area_report, get_place_history, get_place_stats, list_variables, rank_areas, search_places. The pattern is uniform and predictable.

Tool Count5/5

With 9 tools, the set is well-scoped for a statistics server covering search, retrieval, comparison, ranking, and special features like air quality and reports. Each tool earns its place without bloat.

Completeness5/5

The tool surface covers the full workflow: resolving place names, listing available metrics, retrieving current stats, historical trends, area comparisons, ranking, air quality, similar areas, and report downloads. No obvious gaps for a read-only statistics API.

Resources

Need Help?