Skip to main content
Glama

Askdata Xk

by io.github.pipeworx-io
OverviewAdmin

Query Table

query_table
Read-onlyIdempotent

POST a PxWeb query to a Kosovo ASKdata table and return observations as json-stat2. body must be {query:[{code, selection:{filter,values}}], response:{format:'json-stat2'}}. PxWeb caps responses at ~10,000 cells — use codes from table_meta to narrow selections across dimensions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes{query: [{code, selection: {filter, values}}], response: {format: "json-stat2"}}
pathYese.g. "ASKdata/Prices/Consumer Price Index/Annual indicators/T4CPI.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": "Year",
+          "selection": {
+            "filter": "item",
+            "values": [
+              "2022",
+              "2023"
+            ]
+          }
+        }
+      ],
+      "response": {
+        "format": "json-stat2"
+      }
+    },
+    "path": "ASKdata/Prices/Consumer Price Index/Annual indicators/T4CPI.px"
+  }
+]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations indicate readOnly, idempotent, and non-destructive behavior. The description adds value by specifying the HTTP method (POST), the response format, and the size limitation (10,000 cells). No contradictions with annotations are present.

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?

Two concise, information-dense sentences. The first sentence front-loads the purpose, and the second provides essential format and constraint details. No extraneous content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the description mentions the response format 'json-stat2' and the size cap, it does not detail the response structure, error states, or the expected behavior for edge cases. For a tool with no output schema and nested parameters, more completeness could be beneficial.

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 provides a detailed example and descriptions for both parameters. The description reiterates the body format and adds the limitation hint, but does not significantly augment the schema's meaning given 100% schema coverage.

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 clearly states the action: 'POST a PxWeb query to a Kosovo ASKdata table' and specifies the output format 'json-stat2'. It is specific about the resource and verb, and subtly differentiates from sibling 'table_meta' by suggesting its use for narrowing selections.

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?

Explicit instructions on the required body format and the cap of 10,000 cells are given. It references 'use codes from table_meta' to narrow selections, providing clear context on how to use the tool effectively. However, it does not explicitly state when not to use this tool versus alternatives like 'search_within'.

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

All Askdata Xk 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