Skip to main content
Glama

Data Maryland

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Maryland Open Data dataset by resource_id (e.g. "2ir4-626w"). 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. "2ir4-626w" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 100,
-    "resource_id": "2ir4-626w",
-    "where": "year >= 2020"
-  },
-  {
-    "group": "category",
-    "order": "count DESC",
-    "resource_id": "2ir4-626w",
-    "select": "category, count(*) AS count"
-  }
-]New value: +[
+  {
+    "limit": 20,
+    "resource_id": "2ir4-626w"
+  },
+  {
+    "limit": 20,
+    "resource_id": "2ir4-626w",
+    "select": "month"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 100,
+    "resource_id": "2ir4-626w",
+    "where": "year >= 2020"
+  },
+  {
+    "group": "category",
+    "order": "count DESC",
+    "resource_id": "2ir4-626w",
+    "select": "category, count(*) AS count"
+  }
+]
  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 indicate read-only, idempotent, non-destructive behavior. The description adds useful behavioral details beyond that: SoQL clauses are used without the leading $, and the tool returns matching rows as JSON. This helps the agent form correct calls and expectations.

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 with no filler. The core action and resource are front-loaded, followed by the parameter families and return format. Every sentence adds operational value.

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?

For a query tool with rich schema descriptions and safety annotations, the description covers the essential invocation context: target system, required identifier, supported SoQL clauses, pagination controls, and response format. It could explicitly mention that resource_ids come from the datasets tool, but the schema already notes this, so the gap is minor.

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 value by summarizing the SoQL clause parameters (where/select/group/order) and explicitly flagging the syntax nuance about omitting the leading $, which is not in the schema descriptions.

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 states a specific verb (Run), resource (Socrata SoQL query against a Maryland Open Data dataset), and key identifier (resource_id). This clearly distinguishes it from sibling tools like datasets or metadata, which are about discovery rather than querying.

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: use this when you have a resource_id and want to run SoQL queries against Maryland Open Data data. It does not explicitly name alternatives or say when not to use it, but the context is sufficiently clear for an agent to route correctly.

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

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