Skip to main content
Glama

Data Batonrouge

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Baton Rouge Open Data dataset by resource_id (e.g. "fabb-cnnu"). 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. "fabb-cnnu" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 50,
-    "resource_id": "fabb-cnnu",
-    "where": "year >= 2020"
-  },
-  {
-    "group": "category",
-    "order": "total DESC",
-    "resource_id": "fabb-cnnu",
-    "select": "category, count(*) AS total"
-  }
-]New value: +[
+  {
+    "limit": 20,
+    "resource_id": "fabb-cnnu"
+  },
+  {
+    "limit": 20,
+    "resource_id": "fabb-cnnu",
+    "select": "file_number"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 50,
+    "resource_id": "fabb-cnnu",
+    "where": "year >= 2020"
+  },
+  {
+    "group": "category",
+    "order": "total DESC",
+    "resource_id": "fabb-cnnu",
+    "select": "category, 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 cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the description's job is lighter. It still adds real context: the return format (matching rows as JSON) and the Socrata default row cap of 1000. It stops short of auth/rate-limit or error behavior, but that is a minor gap given annotation coverage.

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?

Three tight sentences: purpose first, then the filtering surface, then the return shape. Nothing is redundant with the schema and nothing is padded.

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?

With no output schema, the description compensates by stating that rows come back as JSON, and it names the required identifier. It omits what happens on an invalid resource_id or SoQL error, which is the only material gap for a 7-parameter query tool.

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 description coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: the clause parameters are passed without the leading '$' that the schema's own descriptions use. It also ties limit/offset together as the pagination pair. No syntax detail beyond that is added.

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 and resource: run a Socrata SoQL query against a Baton Rouge Open Data dataset identified by resource_id. The example id ("fabb-cnnu") and the enumerated clauses make it immediately distinguishable from the sibling datasets/metadata tools that enumerate rather than query.

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?

Gives clear context for how to use it — filter via where/select/group/order plus limit/offset — and implies the resource_id comes from the datasets tool. It does not, however, state when to prefer this over alternatives such as search_within, nor any exclusions or prerequisites.

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

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