Skip to main content
Glama

Data Winnipeg

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Winnipeg Open Data dataset by resource_id (e.g. "d4mq-wa44"). 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. "d4mq-wa44" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the JSON return format and the non-obvious 'no leading $' clause convention, which is useful, but it does not discuss rate limits, auth, or error behavior.

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 sentences, front-loaded with the core verb and resource, then the filter mechanics, then the return type. No filler and every sentence carries a distinct piece of 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 7-parameter pass-through query tool with no output schema, the description covers the target, the clause syntax, and the return format adequately. Minor gaps remain around pagination defaults and error handling, but nothing essential to a correct invocation is missing.

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?

Schema description coverage is 100%, and the schema descriptions (with concrete SoQL examples for select/where/order and a documented default limit) are richer than the prose. The description's clause list adds little beyond the schema, so the baseline of 3 applies.

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?

States a specific verb+resource: runs a Socrata SoQL query against a specific dataset identified by resource_id. This clearly distinguishes it from the 'datasets' listing sibling and names the unique input. It stops short of explicitly saying how it differs from neighbors like 'search_within', so it is clear but not sibling-routed.

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?

It implies usage by naming the supported clauses (where/select/group/order plus limit/offset) and the required resource_id, giving an agent enough to attempt a call. However, there is no explicit when-to-use vs when-not-to-use guidance and no named alternative for related lookups, leaving routing to inference.

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

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