Skip to main content
Glama

Datagov Au

by io.github.pipeworx-io

Search

search
Read-onlyIdempotent

Search the data.gov.au CKAN catalogue for Australian open datasets by keyword, with optional Solr filter (e.g. "organization:abs"), sort, and pagination; returns dataset metadata including resource URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqNoSolr filter, e.g. "organization:abs"
rowsNo1-1000 (default 25).
sortNoe.g. "metadata_modified desc"
queryYese.g. "bushfire", "transport".
startNo0-based offset.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoTotal number of packages matching query
resultsNoList of packages (datasets) matching search criteria

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "bushfire"
+  },
+  {
+    "fq": "organization:abs",
+    "query": "transport",
+    "rows": 50,
+    "sort": "metadata_modified desc"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total number of packages matching query",
+      "type": "number"
+    },
+    "results": {
+      "description": "List of packages (datasets) matching search criteria",
+      "items": {
+        "properties": {
+          "author": {
+            "description": "Author name",
+            "type": "string"
+          },
+          "author_email": {
+            "description": "Author email",
+            "type": "string"
+          },
+          "groups": {
+            "description": "Theme groups (categories) for this package",
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "id": {
+            "description": "Package UUID",
+            "type": "string"
+          },
+          "license_id": {
+            "description": "License identifier",
+            "type": "string"
+          },
+          "maintainer": {
+            "description": "Maintainer name",
+            "type": "string"
+          },
+          "maintainer_email": {
+            "description": "Maintainer email",
+            "type": "string"
+          },
+          "metadata_created": {
+            "description": "ISO 8601 creation timestamp",
+            "type": "string"
+          },
+          "metadata_modified": {
+            "description": "ISO 8601 modification timestamp",
+            "type": "string"
+          },
+          "name": {
+            "description": "Package name/slug",
+            "type": "string"
+          },
+          "notes": {
+            "description": "Package description",
+            "type": "string"
+          },
+          "organization": {
+            "properties": {
+              "id": {
+                "description": "Organization UUID",
+                "type": "string"
+              },
+              "name": {
+                "description": "Organization name/slug",
+                "type": "string"
+              },
+              "title": {
+                "description": "Organization display name",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "resources": {
+            "description": "Downloadable resources (files) in package",
+            "items": {
+              "properties": {
+                "description": {
+                  "description": "Resource description",
+                  "type": "string"
+                },
+                "format": {
+                  "description": "File format (e.g. CSV, JSON)",
+                  "type": "string"
+                },
+                "id": {
+                  "description": "Resource UUID",
+                  "type": "string"
+                },
+                "last_modified": {
+                  "description": "ISO 8601 timestamp",
+                  "type": "string"
+                },
+                "name": {
+                  "description": "Resource name",
+                  "type": "string"
+                },
+                "size": {
+                  "description": "File size in bytes",
+                  "type": "number"
+                },
+                "url": {
+                  "description": "Resource download URL",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "tags": {
+            "description": "Tags associated with package",
+            "items": {
+              "properties": {
+                "id": {
+                  "description": "Tag UUID",
+                  "type": "string"
+                },
+                "name": {
+                  "description": "Tag name",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "title": {
+            "description": "Package display title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Package homepage URL",
+            "type": "string"
+          },
+          "version": {
+            "description": "Package version",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds value by disclosing the return type ('dataset metadata including resource URLs') and optional behaviors (filter, sort, pagination). This goes beyond the structured annotations and helps the agent understand what to expect.

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, well-structured sentence that front-loads the main action and resource, then lists optional capabilities and output. Every phrase earns its place, with no redundancy or filler.

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?

With an output schema present and annotation coverage, the description sufficiently covers the tool's purpose, key options, and return type. It doesn't dive into result shape, but that is handled by the output schema. It is complete for a search tool of this complexity.

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 coverage is 100%, so all five parameters have descriptions and examples. The description adds a high-level mapping (keyword, filter, sort, pagination) but does not provide additional detail beyond what the schema already offers. Baseline 3 is appropriate as the schema does the heavy lifting.

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 states a specific verb ('Search') and resource ('data.gov.au CKAN catalogue for Australian open datasets'), and clarifies scope ('by keyword') and output ('returns dataset metadata including resource URLs'). This clearly differentiates from siblings like search_within or package, which target different resources.

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 context: it's for keyword-based searching in the CKAN catalogue with optional Solr filter, sort, and pagination. While it doesn't explicitly mention alternatives or exclusions, the scoping to keyword search on data.gov.au is sufficient for an agent to infer when to use this tool versus more specialized siblings.

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

All Datagov Au 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.

TDQS

B3.2/5.0
Disambiguation3/5

Most tools have detailed descriptions and distinct purposes, but there is overlap among the question-answering tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) and among the six Polymarket-related tools. An agent could reasonably misselect when choosing between the pipeworx variants or between entity_profile and recent_changes.

Naming Consistency4/5

Tool names consistently use snake_case and most follow a verb_noun or noun pattern, with clear domain prefixes like pipeworx_ and polymarket_. Minor deviations include single-word verbs (search, subscribe) and adjective_noun names (recent_alerts, deep_research), but the overall pattern is predictable.

Tool Count2/5

With 37 tools, the server is well beyond the 25+ threshold, and the bulk of them are unrelated to the 'Datagov Au' name. The actual data.gov.au catalogue is served by just six tools (search, package, resource, organizations, groups, tags), while the rest are Pipeworx, Polymarket, memory, subscription, and utility tools — a grossly bloated and miscategorized surface.

Completeness2/5

For a server named Datagov Au, the CKAN tools only cover read-only catalogue lookups; there are no tools for data.gov.au-specific updates, queries, or subscriptions. Conversely, the Pipeworx router exposes access to 5,502 internal tools, but many of those are not directly callable as MCP tools, leaving a confusing gap where discover_tools returns tools the agent cannot actually invoke.

Resources