Skip to main content
Glama

Data Bloomington

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Bloomington Open Data dataset by resource_id (e.g. "yv82-z42g"). 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. "yv82-z42g" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuine value beyond them by disclosing the return shape ('matching rows as JSON'), which is important given there is no output schema, and by noting the '$'-less clause convention. It does not cover auth or rate-limit behavior, so not a 5.

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 sentences, front-loaded with the action and target, then filtering mechanics, then return format. No filler; every sentence carries distinct information.

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 read-only query tool with 100% schema coverage, four safety annotations and no output schema, the description supplies the missing return format and the SoQL clause convention. Only minor gaps remain (pagination limits beyond the schema's offset note, provenance of resource_id), keeping it from a 5.

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 real meaning: it maps the free-text filter clauses (where/select/group/order plus limit/offset) and clarifies that the clauses are passed 'without the leading $', which the schema does not state. That $ convention is a non-obvious usage detail beyond the schema.

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?

States a specific verb and resource: 'Run a Socrata SoQL query against a Bloomington Open Data dataset by resource_id', naming the exact query dialect and target. It is easily distinguished from sibling tools (datasets, metadata), though it does not explicitly name or defer to them, which keeps it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies when to use it (to filter/retrieve dataset rows) and enumerates the clause vocabulary, but offers no explicit when-to-use vs when-not guidance and never references alternatives such as datasets or metadata for discovery. Usage is inferable rather than stated.

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

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