Skip to main content
Glama

Data Howardcounty

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Howard County Open Data dataset by resource_id (e.g. "qccx-65fg"). 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. "qccx-65fg" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 100,
-    "resource_id": "qccx-65fg",
-    "where": "year >= 2020"
-  },
-  {
-    "group": "category",
-    "order": "count DESC",
-    "resource_id": "qccx-65fg",
-    "select": "category, count(*) AS count"
-  }
-]New value: +[
+  {
+    "limit": 20,
+    "resource_id": "qccx-65fg"
+  },
+  {
+    "limit": 20,
+    "resource_id": "qccx-65fg",
+    "select": "date_reported"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 100,
+    "resource_id": "qccx-65fg",
+    "where": "year >= 2020"
+  },
+  {
+    "group": "category",
+    "order": "count DESC",
+    "resource_id": "qccx-65fg",
+    "select": "category, count(*) AS count"
+  }
+]
  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 declare readOnly/idempotent/non-destructive, and the description adds useful behavior beyond that: it returns JSON rows, takes SoQL clauses 'without the leading $', and supports limit/offset. This gives an agent the key operational detail that could cause errors if omitted.

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 front-loaded sentences with no filler: action, resource identifier format, supported clauses, and return type. Every phrase earns its place.

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 query tool with 7 fully documented parameters, the description covers the essential context: target dataset, syntax rules, pagination options, and JSON return. No output schema exists, so stating the return format is important and is done.

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, but the description adds meaning by explicitly stating that SoQL clauses are passed 'without the leading $' and by grouping where/select/group/order plus limit/offset. This prevents a likely mistake given the schema's '$where' style descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: 'Run a Socrata SoQL query against a Howard County Open Data dataset by resource_id', and it clarifies the output is JSON. It is clearly distinct from siblings like datasets/metadata, though it does not explicitly name an alternative tool.

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 need to query a specific Howard County dataset by resource_id, with SoQL filters and limit/offset. It implies the workflow from the sibling datasets tool, but it does not explicitly state when not to use it or name alternatives.

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

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