Skip to main content
Glama

Data Novascotia

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Nova Scotia Open Data dataset by resource_id (e.g. "3nka-59nz"). 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. "3nka-59nz" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing the return format ('Returns matching rows as JSON') and the soql syntax requirement (no leading '$'), which are behavioral details beyond the structured 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?

A single compact sentence that front-loads the core action and resource, then efficiently packs supported clauses, a syntax rule, and the return type. No filler or redundancy.

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 query tool with no output schema, the description covers the key usage points: target dataset, filter clauses, syntax caveat, and JSON return. It does not restate default row limits (already in the schema) and could explicitly mention that resource_id typically comes from the 'datasets' tool, but nothing essential is missing for a correct invocation.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful syntax guidance: it clarifies that the SoQL clauses should be supplied 'without the leading $', a detail not explicit in the schema property descriptions. It also ties the parameters together as a filter/query set.

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 opens with a specific verb ('Run a Socrata SoQL query') against a clearly identified resource ('Nova Scotia Open Data dataset by resource_id'). It lists the filter capabilities and return type, making it unmistakably distinct from sibling tools like datasets and metadata.

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 clear operational context: how to target a dataset (resource_id), which SoQL clauses are supported, and the constraint to omit the leading '$'. It does not explicitly name alternatives or say 'use this instead of datasets', but the purpose is specific enough that an agent can infer when it applies.

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

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