Skip to main content
Glama

Data Mesa

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Mesa Open Data dataset by resource_id (e.g. "2gkz-7z4f"). 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. "2gkz-7z4f" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 100,
-    "resource_id": "2gkz-7z4f",
-    "where": "year >= 2020"
-  },
-  {
-    "group": "department",
-    "order": "total DESC",
-    "resource_id": "2gkz-7z4f",
-    "select": "department, count(*) AS total"
-  }
-]New value: +[
+  {
+    "limit": 20,
+    "resource_id": "2gkz-7z4f"
+  },
+  {
+    "limit": 20,
+    "resource_id": "2gkz-7z4f",
+    "select": "rowid"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 100,
+    "resource_id": "2gkz-7z4f",
+    "where": "year >= 2020"
+  },
+  {
+    "group": "department",
+    "order": "total DESC",
+    "resource_id": "2gkz-7z4f",
+    "select": "department, count(*) AS total"
+  }
+]
  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 declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context by specifying that results are returned as JSON and that SoQL clauses must be provided without the leading $, which prevents common invocation errors. No contradiction with annotations exists.

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 a single, front-loaded sentence that names the action and resource first, then explains filter syntax, and ends with the return format. Every phrase earns its place and there is no redundant or vague filler.

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 rich schema (7 fully described parameters, examples, required field), the strong annotations, and the absence of an output schema, the description is complete enough for correct invocation. It states the query language, clause syntax, pagination options, and JSON return format, leaving no major operational gap.

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 parameters are already documented well. The description adds meaning beyond the schema by clarifying that where/select/group/order are SoQL clauses without the leading $, and by framing limit/offset as pagination controls. This helps the agent construct valid queries.

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 uses the specific verb 'Run' and identifies the exact resource: a Socrata SoQL query against a Mesa Open Data dataset by resource_id. This clearly distinguishes it from sibling tools like datasets or metadata, which list or describe datasets rather than query rows.

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 clearly implies the tool is for executing SoQL queries with filtering clauses, but it does not explicitly state when to use this over alternatives such as datasets, metadata, or search_within. There is no when-not-to-use guidance or named alternative, so the usage context is inferred rather than explicit.

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

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