Skip to main content
Glama

Data Providence

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Providence Open Data dataset by resource_id (e.g. "vank-fyx9"). 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. "vank-fyx9" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 100,
-    "resource_id": "vank-fyx9",
-    "where": "year >= 2020"
-  },
-  {
-    "group": "category",
-    "order": "total DESC",
-    "resource_id": "vank-fyx9",
-    "select": "category, count(*) AS total"
-  }
-]New value: +[
+  {
+    "limit": 20,
+    "resource_id": "vank-fyx9"
+  },
+  {
+    "limit": 20,
+    "resource_id": "vank-fyx9",
+    "select": "arrest_date"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 100,
+    "resource_id": "vank-fyx9",
+    "where": "year >= 2020"
+  },
+  {
+    "group": "category",
+    "order": "total DESC",
+    "resource_id": "vank-fyx9",
+    "select": "category, count(*) AS total"
+  }
+]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, so the description's added value lies in disclosing the JSON return format and the non-obvious SoQL syntax convention (no leading $). This supplements the structured data without contradiction.

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 with no fluff. It front-loads the core purpose and example, then concisely enumerates the key query options. Every clause 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?

The description covers the essential behavior for a read-only query tool: resource selection, filter/group/order clauses, pagination, and output format. Some details like error behavior or rate limits are absent, but the high schema coverage and simple tool shape make this adequate.

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 each parameter is already documented. The description adds interpretative context by grouping where/select/group/order as SoQL clauses and clarifying the no-$ rule, which helps construct valid queries beyond what the schema alone provides.

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 names a specific verb ('Run'), a specific resource ('Socrata SoQL query against a Providence Open Data dataset by resource_id'), and gives a concrete example ID. This clearly distinguishes the tool from siblings like datasets or metadata, even without explicitly naming them.

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 explains how to use the tool (SoQL clauses without leading $, limit/offset) but does not explicitly state when to prefer it over sibling tools. The use case is implied rather than directly contrasted with alternatives.

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

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