Skip to main content
Glama

Makstat Mk

by io.github.pipeworx-io
OverviewAdmin

Query Table

query_table
Read-onlyIdempotent

POST a PxWeb query to a MakStat (North Macedonia statistics) table and return observations as json-stat2. body must be {query:[{code, selection:{filter,values}}], response:{format:'json-stat2'}}. PxWeb enforces a cell-count limit — narrow each dimension's values using codes from table_meta to avoid rejection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes{query: [{code, selection: {filter, values}}], response: {format: "json-stat2"}}
pathYese.g. "Naselenie/VencaniRazvedeni/280_VitStat_Brak_voz_ml.px"

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "body": {
+      "query": [
+        {
+          "code": "Voz",
+          "selection": {
+            "filter": "item",
+            "values": [
+              "1",
+              "2"
+            ]
+          }
+        },
+        {
+          "code": "God",
+          "selection": {
+            "filter": "item",
+            "values": [
+              "2020",
+              "2021"
+            ]
+          }
+        }
+      ],
+      "response": {
+        "format": "json-stat2"
+      }
+    },
+    "path": "Naselenie/VencaniRazvedeni/280_VitStat_Brak_voz_ml.px"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds the behavioral trait of a cell-count limit and clarifies that the POST request is effectively a query, providing context beyond annotations.

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 two sentences, front-loaded with purpose, and each sentence provides essential information without redundancy.

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?

The description covers the body format and key constraint (cell-count limit). It lacks details about the response structure beyond format, but the output format is stated. For a tool with no output schema, this is adequate.

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 100% and the description does not add additional meaning to the parameters beyond what the schema already specifies. The description restates the body format but does not explain individual fields.

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 states the action ('POST a PxWeb query'), the resource ('MakStat table'), and the output format ('json-stat2'). It distinguishes from sibling tools like table_meta, which likely provides metadata.

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 provides explicit guidance on narrowing dimension values using codes from table_meta and warns about the cell-count limit. It implies a prerequisite but does not explicitly state when to use or avoid this tool.

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

All Makstat Mk toolsInspect
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.

Resources