Skip to main content
Glama

Data Delaware

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Delaware Open Data dataset by resource_id (e.g. "5zy2-grhr"). 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. "5zy2-grhr" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 100,
-    "resource_id": "5zy2-grhr",
-    "where": "year >= 2020"
-  },
-  {
-    "group": "category",
-    "order": "count DESC",
-    "resource_id": "5zy2-grhr",
-    "select": "category, COUNT(*) AS count"
-  }
-]New value: +[
+  {
+    "limit": 20,
+    "resource_id": "5zy2-grhr"
+  },
+  {
+    "limit": 20,
+    "resource_id": "5zy2-grhr",
+    "select": "business_name"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 100,
+    "resource_id": "5zy2-grhr",
+    "where": "year >= 2020"
+  },
+  {
+    "group": "category",
+    "order": "count DESC",
+    "resource_id": "5zy2-grhr",
+    "select": "category, COUNT(*) AS count"
+  }
+]
  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 the safety profile (read-only, idempotent, non-destructive), so the bar is lower. The description adds meaningful behavior: SoQL clauses must be passed without the leading '$', limit/offset are available, and the result shape is JSON.

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 dense sentences that front-load the core operation and syntax caveat, then finish with the return type. There is no filler or redundant restating of schema details.

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 read-only SoQL query tool, the description, full schema, and examples provide everything needed to invoke it correctly: required resource_id, supported clauses, no-'$' convention, pagination controls, and JSON return type. The absence of an output schema is mitigated by explicitly stating the return format.

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 schema covers all 7 parameters with descriptions and examples, so the baseline is 3. The description adds the key syntax convention (omit the leading '$') and maps where/select/group/order plus limit/offset to the expected parameters, reinforcing the schema without repeating it.

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?

Description opens with a specific verb and resource: 'Run a Socrata SoQL query against a Delaware Open Data dataset', names the required resource_id with an example, and enumerates the query clauses. This clearly distinguishes it from generic siblings like metadata or datasets even without 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It establishes clear usage context: queries are scoped to a specific Delaware Open Data dataset via resource_id and use SoQL filtering plus pagination. It implies dataset discovery first, but it does not explicitly state when to prefer this tool over siblings such as metadata or datasets.

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

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