Skip to main content
Glama
Sign In

Data Usdot

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

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

Input 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. "4zfz-amsd" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive safety profile. The description adds useful behavior: it returns JSON rows, supports where/select/group/order plus limit/offset, and clarifies that SoQL clauses must omit the leading $. This goes beyond the annotation-only safety profile.

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 sentences, front-loaded with the action and resource, then a compact list of supported clauses and output format. No filler or redundant restatement of schema details.

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?

Given that all 7 parameters are fully described in the schema and the description covers the query dialect, example resource id, and JSON return format, not much is missing. It could have referenced output pagination defaults or linkage to the 'datasets' tool for finding resource_ids, but these are minor and the schema already documents the defaults.

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 the crucial convention that SoQL clauses are passed without the leading $, which is not stated in any schema property description and prevents a common error. It also names the specific clause parameters (where/select/group/order) and 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 opens with a specific verb-resource pair: 'Run a Socrata SoQL query against a US DOT Open Data dataset by resource_id' and includes a concrete example id. This clearly separates the tool from sibling dataset-discovery tools like 'datasets' and 'metadata,' which are about finding datasets and their descriptions rather than querying rows.

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 specifies the context: use resource_id from a US DOT dataset and apply SoQL clauses without $. It does not explicitly state exclusions or name alternatives, so it falls short of a full 5, but the intended usage is unmistakable.

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

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