Skip to main content
Glama

Hagstofa Is

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query Table

query_table
Read-onlyIdempotent

Pull data from a table (path includes the ".px" suffix). body is a PxWeb query object. PxWeb limits request size — filter dimensions to keep the cell count small.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes{query: [{code, selection: {filter, values}}], response: {format: "json-stat2"}}
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "body": {
-      "query": [
-        {
-          "code": "Ar",
-          "selection": {
-            "filter": "item",
-            "values": [
-              "2020",
-              "2021",
-              "2022"
-            ]
-          }
-        }
-      ],
-      "response": {
-        "format": "json-stat2"
-      }
-    },
-    "path": "Ibuar/mannfjoldi/1_yfirlit/yfirlit_mannfjolda/MAN00000.px"
-  }
-]New value: +[
+  {
+    "body": {
+      "query": [
+        {
+          "code": "Ár",
+          "selection": {
+            "filter": "item",
+            "values": [
+              "2024",
+              "2025",
+              "2026"
+            ]
+          }
+        },
+        {
+          "code": "Eining",
+          "selection": {
+            "filter": "item",
+            "values": [
+              "0"
+            ]
+          }
+        }
+      ],
+      "response": {
+        "format": "json-stat2"
+      }
+    },
+    "path": "Ibuar/mannfjoldi/1_yfirlit/yfirlit_mannfjolda/MAN00000.px"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "body": {
+      "query": [
+        {
+          "code": "Ar",
+          "selection": {
+            "filter": "item",
+            "values": [
+              "2020",
+              "2021",
+              "2022"
+            ]
+          }
+        }
+      ],
+      "response": {
+        "format": "json-stat2"
+      }
+    },
+    "path": "Ibuar/mannfjoldi/1_yfirlit/yfirlit_mannfjolda/MAN00000.px"
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish the tool is read-only, idempotent, and non-destructive. The description adds useful operational context beyond annotations: PxWeb imposes request-size limits, so agents should keep the cell count small by filtering dimensions. This is a meaningful behavioral constraint not present in the structured metadata.

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 with no wasted words; every clause carries information: the action, the path suffix, the body type, and the request-size warning. It is easy to parse and appropriately front-loaded.

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 two-parameter read tool, the description covers the essential resource identifier and the key operational constraint, with the schema example filling in the body structure in detail. It could be more complete by naming metadata-related siblings or describing return format, but nothing critical to making a correct call is missing.

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 coverage is 50%, and the description adds meaning to the path parameter by noting it must include the '.px' suffix, while also characterizing body as a PxWeb query object. It does not elaborate on constructing selections or handling response formats beyond what the schema example already provides, so compensation is only partial.

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 opens with a specific action ('Pull data') and identifies the resource type ('a table' with the '.px' suffix), making the tool's core function clear. It does not explicitly contrast with siblings such as table_meta or search_within, so it stops short of full differentiation.

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?

The description implies this tool is for fetching data values from a table and gives practical guidance to filter dimensions because PxWeb limits request size. However, it does not explicitly say when to use this tool over siblings like table_meta, nor does it state exclusions.

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

All Hagstofa Is 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