Skip to main content
Glama

Data Texas

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Texas Open Data dataset by resource_id (e.g. "54pj-3dxy"). 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. "54pj-3dxy" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds valuable beyond-annotation context: return format is 'matching rows as JSON', and SoQL clauses must be provided without the leading $ sign. These are concrete behavioral details that help the agent invoke the tool correctly.

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 sentences front-load the core purpose and then add the most operationally important syntax detail. Every clause earns its place; there is 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 no output schema, the description adequately covers the invocation pattern: required resource_id, the SoQL clauses, pagination controls, and the JSON result format. Combined with the fully detailed input schema and the read-only/idempotent annotations, an agent has enough information to call 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?

The input schema has 100% documented parameters, so the baseline is 3. The description adds extra meaning by grouping where/select/group/order and clarifying that all accept SoQL clauses without the leading $, which is not obvious from individual schema descriptions. It thus improves parameter understanding without explaining every parameter.

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?

States a specific verb ('Run'), a clear resource ('a Socrata SoQL query against a Texas Open Data dataset'), and identifies the required resource_id with an example. The purpose is unambiguous and naturally distinguishes this data-row querying tool from sibling metadata/dataset-listing tools.

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 implicitly tells the agent to use this tool when it needs to filter or query rows from a Texas Open Data dataset by resource_id, and it mentions SoQL clauses and limit/offset. It does not explicitly name sibling alternatives or state when-not-to-use it, so the guidance remains 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 Data Texas 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