Skip to main content
Glama

Data Fulton

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "resource_id": "ey9v-j62i"
-  },
-  {
-    "limit": 50,
-    "resource_id": "ey9v-j62i",
-    "select": "name, amount",
-    "where": "year >= 2020"
-  }
-]New value: +[
+  {
+    "limit": 5,
+    "resource_id": "ey9v-j62i"
+  },
+  {
+    "limit": 5,
+    "resource_id": "ey9v-j62i",
+    "select": "nodeid"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "resource_id": "ey9v-j62i"
+  },
+  {
+    "limit": 50,
+    "resource_id": "ey9v-j62i",
+    "select": "name, amount",
+    "where": "year >= 2020"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds valuable behavioral context: queries are formatted without the leading '$', results are returned as JSON, and the target is a specific Socrata open-data portal. This goes beyond the annotations without contradicting them.

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 first sentence fronts the core operation and resource, the second covers filtering and output. Every clause 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?

Given the moderate complexity of a SoQL query tool, the description covers the operation, target resource, accepted clauses, output format, and a key formatting rule. The schema supplements with parameter details and examples, so nothing essential is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema coverage is 100%, with each parameter already described. The description adds a useful formatting caveat ('without the leading $') and lists the clause names, but it does not substantially deepen parameter meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 and resource: 'Run a Socrata SoQL query against a Fulton County Open Data dataset by resource_id.' It further enumerates the filter capabilities and the JSON output, making the tool's role unambiguous and distinct from sibling tools like datasets or metadata.

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 a clear usage context: use it to query a specific dataset by resource_id with SoQL filtering. It does not explicitly name alternatives or when-not-to-use conditions, but the context is sufficiently clear for an agent to select it appropriately.

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

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