Skip to main content
Glama

Statfin Fi

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Subjects

subjects
Read-onlyIdempotent

Browse the Statistics Finland (StatFin) subject tree of Finnish official statistics — population, education, employment, consumer prices, housing, health and national accounts tables published by Tilastokeskus. Entries with type "l" are folders (drill in with their id, e.g. "vkour" for educational structure of population, "khi" for the consumer price index); type "t" are tables whose id is the bare 4-character code plus ".px" (e.g. "15ig.px"), which you pass to table_meta and query_table as "folder/table.px" — for example "vkour/15ig.px".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoSub-path under /StatFin/ (default empty = root list of ~135 subject folders). e.g. "vkour" or "khi".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "path": ""
-  },
-  {
-    "path": "khi"
-  }
-]New value: +[
+  {
+    "path": ""
+  },
+  {
+    "path": "vkour"
+  }
+]
    • changedInput schema / properties / path / description
      Previous value: -"Sub-path under /StatFin/ (default empty = root). e.g. \"khi\" or \"synt\"."New value: +"Sub-path under /StatFin/ (default empty = root list of ~135 subject folders). e.g. \"vkour\" or \"khi\"."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "path": ""
+  },
+  {
+    "path": "khi"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructiveness, so the description does not need to restate those. It adds valuable behavior details: the distinction between folder and table entries, the format of IDs, and how to combine paths (e.g., 'vkour/15ig.px'). This goes beyond the structured annotations and helps the agent predict output structure and integration with other tools.

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?

The description is moderately long but each sentence serves a purpose: stating the purpose, defining the two entry types, and giving concrete examples. It is front-loaded with the primary function and then details, making it easy to scan. It is appropriately sized for the complexity of the tool.

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?

For a tree-browsing tool with no output schema, the description provides enough context: it explains what the entries are, how to navigate, and how to use the returned IDs with other tools. It does not describe the exact structure of the response (e.g., fields like name, childCount), but the essential behavior is covered. Given the tool's simplicity and the annotations (openWorldHint), this is nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already covers the 'path' parameter with a description and examples (coverage 100%). The tool description enriches it by explaining the meaning of folder IDs (e.g., 'vkour' for education) and how they are used to drill in, adding context beyond the schema's basic definition. This is a meaningful enhancement over the baseline of 3.

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 explicitly states the tool browses the StatFin subject tree, lists the topics covered, and distinguishes folders (type 'l') from tables (type 't'). It also differentiates itself from siblings by explaining that table IDs are passed to table_meta and query_table, making it clear this tool is for discovery, not querying.

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 clear context on when to use the tool—to browse and drill into the subject tree—and implicitly states that table IDs from here are used with table_meta/query_table. It does not explicitly enumerate alternatives or exclusions, but the examples and mention of downstream tools provide strong usage guidance.

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

All Statfin Fi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources