Skip to main content
Glama

Stat Lv

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query Table

query_table
Read-onlyIdempotent

Pull data from a table. body is a PxWeb query object. Use the bare table path with no ".px" suffix.

Input Schema

NameRequiredDescriptionDefault
bodyYes{query: [{code, selection: {filter, values}}], response: {format: "json-stat2"}}
pathYese.g. "OSP_PUB/POP/IR/IRS/IRS010"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "body": {
-      "query": [
-        {
-          "code": "Gads",
-          "selection": {
-            "filter": "item",
-            "values": [
-              "1"
-            ]
-          }
-        }
-      ],
-      "response": {
-        "format": "json-stat2"
-      }
-    },
-    "path": "OSP_PUB/POP/IR/IRS/IRS010"
-  }
-]New value: +[
+  {
+    "body": {
+      "query": [
+        {
+          "code": "INDICATOR",
+          "selection": {
+            "filter": "item",
+            "values": [
+              "POP_SY"
+            ]
+          }
+        },
+        {
+          "code": "ContentsCode",
+          "selection": {
+            "filter": "item",
+            "values": [
+              "IRS010"
+            ]
+          }
+        },
+        {
+          "code": "TIME",
+          "selection": {
+            "filter": "item",
+            "values": [
+              "2024",
+              "2025",
+              "2026"
+            ]
+          }
+        }
+      ],
+      "response": {
+        "format": "json-stat2"
+      }
+    },
+    "path": "OSP_PUB/POP/IR/IRS/IRS010"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "body": {
+      "query": [
+        {
+          "code": "Gads",
+          "selection": {
+            "filter": "item",
+            "values": [
+              "1"
+            ]
+          }
+        }
+      ],
+      "response": {
+        "format": "json-stat2"
+      }
+    },
+    "path": "OSP_PUB/POP/IR/IRS/IRS010"
+  }
+]
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint), so the bar is lower. The description adds behavioral context by specifying the request format (PxWeb query object, path convention), but does not disclose return shape, pagination, or error behavior beyond what annotations imply.

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 short sentences with no filler. The primary action is front-loaded, and the critical path-format caveat is placed immediately after. Every phrase earns its place.

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?

With only 2 parameters, 100% schema coverage, and rich annotations, the description covers the essential operational details. The only notable gap is the lack of any description of return values, but the body schema example implies json-stat2 response format, and no output schema exists to demand more.

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 baseline is 3. The description adds semantic value by clarifying that 'body' is a PxWeb query object and that 'path' must omit the .px suffix, enriching the bare schema definitions. The example in the schema demonstrates the structure, but the description's path nuance is not present elsewhere.

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 states a specific verb and resource: 'Pull data from a table', which clearly indicates the tool extracts table data. It adds useful constraints like 'body is a PxWeb query object' and 'bare table path', but does not explicitly differentiate it from sibling tools such as table_meta or search_within.

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 gives a clear operational instruction: use the bare table path without the .px suffix and provide a PxWeb query object as body. However, it offers no guidance on when to choose this tool over alternatives like table_meta or subjects; usage context is implied rather than explicit.

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

All Stat Lv 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