Skip to main content
Glama

Data Fortworth

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Fort Worth Open Data dataset by resource_id (e.g. "eax3-qev8"). 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. "eax3-qev8" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 100,
+    "resource_id": "eax3-qev8",
+    "where": "year >= 2020"
+  },
+  {
+    "group": "category",
+    "order": "n DESC",
+    "resource_id": "eax3-qev8",
+    "select": "category, count(*) AS n"
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, covering safety. The description adds that returns are JSON, which is useful but not extensive. No additional behavioral details (e.g., pagination defaults, rate limits) are provided, but annotations lower the bar.

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 that efficiently convey the core purpose, input format, and output. No extraneous words; key information is front-loaded.

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?

Given the complexity (7 parameters, no output schema) and annotations, the description covers the essential aspects: tool action, dataset identification, filtering options, and return format. It lacks details on pagination behavior or error handling, but the schema examples and annotations mitigate gaps significantly.

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 has 100% coverage with descriptions for all 7 parameters. The description adds the nuance that SoQL clauses should not include the leading '$', which is helpful. Beyond that, it does not elaborate on parameter specifics, but the schema already provides adequate definitions.

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 identifies the tool as executing a Socrata SoQL query against a specific Fort Worth Open Data dataset using a resource_id. It lists supported SoQL clauses and explicitly states the output format (JSON), distinguishing it from sibling tools that serve different databases or tasks.

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 clearly states when to use the tool (to query a Socrata dataset by resource_id) and implies usage context (filtering with SoQL clauses). However, it does not explicitly mention when not to use it or provide alternatives, though sibling tools are clearly different in domain.

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

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