Skip to main content
Glama

Data Fulton

by io.github.pipeworx-io
OverviewAdmin

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. Dates show when Glama detected each change.

  1. 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"
+  }
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds that results are returned as JSON and notes SoQL clauses should omit the leading '$', which is a behavioral detail beyond annotations. It does not contradict annotations.

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?

The description is two sentences: the first explains the tool's action and inputs, the second states the output. It is front-loaded and contains no extraneous details, making it easy to parse quickly.

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?

With 7 parameters, 1 required, full schema coverage, and no output schema, the description sufficiently covers the tool's purpose, usage pattern, and output format. It provides enough context for an agent to select and invoke the tool correctly.

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% with individual parameter descriptions. The description adds context by grouping parameters into SoQL clauses and pagination, and clarifies the syntax convention (omit '$'), enhancing understanding beyond the schema alone.

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 clearly states the tool runs a Socrata SoQL query against a specific dataset by resource_id, giving an example. It specifies the verb ('run a query') and resource ('dataset'), and lists query capabilities (where/select/group/order/limit/offset). This is specific and distinguishes from sibling tools like 'datasets' which list available datasets.

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 explains the tool is used to query dataset data, but does not explicitly state when to use it versus alternatives or provide exclusion criteria. It implies its purpose but lacks explicit usage guidance, such as 'use datasets to find resource_id, then use query to fetch data'.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources