Skip to main content
Glama
Sign In

Data Orlando

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Orlando Open Data dataset by resource_id (e.g. "ryhf-m453"). Filter with where/select/group/order (SoQL clauses, without the leading $) plus limit/offset. Returns matching rows as JSON.

Input 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. "ryhf-m453" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "resource_id": "ryhf-m453",
-    "where": "year >= 2020"
-  },
-  {
-    "group": "category",
-    "limit": 50,
-    "order": "n DESC",
-    "resource_id": "ryhf-m453",
-    "select": "name, count(*) AS n"
-  }
-]New value: +[
+  {
+    "limit": 5,
+    "resource_id": "ryhf-m453"
+  },
+  {
+    "limit": 5,
+    "resource_id": "ryhf-m453",
+    "select": "permit_number"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "resource_id": "ryhf-m453",
+    "where": "year >= 2020"
+  },
+  {
+    "group": "category",
+    "limit": 50,
+    "order": "n DESC",
+    "resource_id": "ryhf-m453",
+    "select": "name, count(*) AS n"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds useful context beyond that: it returns JSON rows and explains the SoQL clause syntax. No contradiction with 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?

Three short, front-loaded sentences cover purpose, usage syntax, and return format with no redundancy. Every sentence contributes essential 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 full schema coverage, the description is largely complete: it states the query target, clause syntax, and output format. It could be stronger by referencing related sibling tools or Socrata-specific limitations, but the essential calling context is present.

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?

Input schema covers 100% of parameters, providing a baseline of 3. The description adds value by explaining that SoQL clauses should be passed without the leading $, and by grouping the parameters into their functional roles.

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?

Description clearly states the tool runs a Socrata SoQL query against an Orlando Open Data dataset by resource_id, and mentions returning matching rows as JSON. It is specific about verb and resource, but does not explicitly distinguish itself from sibling tools like search_within or datasets.

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 practical guidance: filter with where/select/group/order plus limit/offset, and omit the leading $ in SoQL clauses. It provides clear context for using the tool, though it does not explicitly state when to prefer alternatives or include exclusions.

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

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