Skip to main content
Glama

Data Wa

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Washington State Open Data dataset by resource_id (e.g. "qxh8-f4bd"). Filter with where/select/group/order (SoQL clauses, without the leading $) plus limit/offset. Returns matching rows as JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupNoSoQL $group column(s).
limitNoMax rows (default Socrata 1000).
orderNoSoQL $order, e.g. "date DESC".
whereNoSoQL $where filter, e.g. "year >= 2020 AND status = 'Active'".
offsetNoPagination offset.
selectNoSoQL $select, e.g. "name, count(*) AS n".
resource_idYesDataset id, e.g. "qxh8-f4bd" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 100,
-    "resource_id": "qxh8-f4bd",
-    "where": "year >= 2020"
-  },
-  {
-    "group": "name",
-    "order": "total DESC",
-    "resource_id": "qxh8-f4bd",
-    "select": "name, count(*) AS total"
-  }
-]New value: +[
+  {
+    "limit": 20,
+    "resource_id": "qxh8-f4bd"
+  },
+  {
+    "limit": 20,
+    "resource_id": "qxh8-f4bd",
+    "select": "credentialnumber"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 100,
+    "resource_id": "qxh8-f4bd",
+    "where": "year >= 2020"
+  },
+  {
+    "group": "name",
+    "order": "total DESC",
+    "resource_id": "qxh8-f4bd",
+    "select": "name, count(*) AS total"
+  }
+]
  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 cover readOnly, openWorld, idempotent, and non-destructive behavior. The description adds value beyond annotations by confirming the tool returns matching rows as JSON and by clarifying that SoQL clauses must be passed without the leading '$'—an important behavioral detail for correct invocation.

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 compact sentences front-load the action and target resource, specify the key filtering options, and state the output format. Every sentence contributes operational value with no filler or redundancy.

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 query tool with 7 parameters, the description plus 100% schema coverage and meaningful annotations is complete. It identifies the dataset source, the query language, the syntax nuance (no leading $), and the JSON return format. No additional context is needed for an agent to invoke it correctly.

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 description coverage is 100%, so the baseline is 3. The description earns a 4 by adding semantic guidance beyond the schema: it groups where/select/group/order as SoQL clauses, explicitly notes that the leading '$' must be omitted, and pairs limit/offset as pagination controls.

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 a specific verb and resource: 'Run a Socrata SoQL query against a Washington State Open Data dataset by resource_id'. It further differentiates the tool by explaining the SoQL filtering capabilities and the JSON return format, so an agent can distinguish it from sibling tools like datasets or 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 gives clear context for when to use the tool: when you have a resource_id and need to query rows with SoQL filters. It does not explicitly name alternatives or exclusions, but the specificity of 'Socrata SoQL query against... dataset by resource_id' is enough to imply appropriate use versus sibling metadata/search tools.

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

All Data Wa 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