Skip to main content
Glama

Hagstova Fo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query Table

query_table
Read-onlyIdempotent

POST a PxWeb query to a Hagstova Føroya table and return observations as json-stat2. body must be {query:[{code, selection:{filter,values}}], response:{format:'json-stat2'}}. PxWeb rejects requests exceeding its cell limit — narrow each dimension's selection.values using codes from table_meta.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes{query: [{code, selection: {filter, values}}], response: {format: "json-stat2"}}
pathYese.g. "H2/UO/UO01/land_oyfj.px"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "body": {
-      "query": [
-        {
-          "code": "Municipality",
-          "selection": {
-            "filter": "item",
-            "values": [
-              "0"
-            ]
-          }
-        }
-      ],
-      "response": {
-        "format": "json-stat2"
-      }
-    },
-    "path": "H2/UO/UO01/land_oyfj.px"
-  }
-]New value: +[
+  {
+    "body": {
+      "query": [
+        {
+          "code": "island/highest mountain",
+          "selection": {
+            "filter": "item",
+            "values": [
+              "999"
+            ]
+          }
+        },
+        {
+          "code": "area in km², no. of mountains and population",
+          "selection": {
+            "filter": "item",
+            "values": [
+              "001"
+            ]
+          }
+        }
+      ],
+      "response": {
+        "format": "json-stat2"
+      }
+    },
+    "path": "H2/UO/UO01/land_oyfj.px"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "body": {
+      "query": [
+        {
+          "code": "Municipality",
+          "selection": {
+            "filter": "item",
+            "values": [
+              "0"
+            ]
+          }
+        }
+      ],
+      "response": {
+        "format": "json-stat2"
+      }
+    },
+    "path": "H2/UO/UO01/land_oyfj.px"
+  }
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond the annotations by disclosing that PxWeb rejects cell-limit-exceeding requests and that responses come back as json-stat2.

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 compact and front-loaded with the primary action, then gives the request contract and the key constraint. Every sentence earns its place, with no redundant phrasing.

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 read-only query tool with no output schema, the description is complete: it states the action, the request format, the output format, and the main failure mode. The reference to table_meta gives the agent a clear path to obtain dimension codes, and the schema example covers the path parameter.

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?

Schema coverage is 100%, so the schema already documents both parameters. The description adds value by specifying the exact required body shape and by giving the practical instruction to use table_meta codes to keep each selection within limits.

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 names a specific verb ('POST'), a specific resource ('a Hagstova Føroya table'), and the exact expected output ('observations as json-stat2'). It clearly separates this tool from siblings like table_meta by describing a data-query action rather than a metadata lookup.

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 actionable usage context: it warns about PxWeb's cell limit and directs the agent to narrow selection.values using codes from table_meta. It does not explicitly list alternative tools or state when not to use it, but the workflow is clear enough for an agent to select it appropriately.

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

All Hagstova Fo 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