Skip to main content
Glama

Datagov Au

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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.

  1. Changed7 schema fields changed
    • changedOutput schema / properties / results / items / properties / author_email / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / results / items / properties / maintainer / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / results / items / properties / maintainer_email / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / results / items / properties / resources / items / properties / last_modified / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / results / items / properties / resources / items / properties / size / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedOutput schema / properties / results / items / properties / url / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / results / items / properties / version / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  2. 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"
+}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds value beyond the annotations by specifying the return payload (dataset metadata including resource URLs) and clarifying the nature of the optional filter (Solr query syntax). It does not contradict any annotations and adds meaningful behavioral context without redundancy.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that efficiently packs the core purpose, optional features, and return type. It is front-loaded with the main action and resource, and the details are given in a natural order. It is concise without omit ting critical information, though it could be slightly more structured by separating clauses, but overall it is well-balanced.

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?

For a tool with 5 parameters, an output schema, and rich annotations, the description covers all essential aspects: the catalogue, the search keyword, optional Solr filter, sort, pagination, and the return of metadata with resource URLs. Since an output schema exists, the description does not need to explain return values in detail. The description is complete for an agent to call the tool correctly and understand its scope.

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?

The input schema has 100% description coverage; every parameter (fq, rows, sort, query, start) is already described in the schema. The description restates some of these (e.g., gives an example for fq and mentions pagination) but does not add new semantic information beyond what the schema provides. According to the baseline rule, a 3 is appropriate when 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 clearly states the verb 'Search', the resource 'data.gov.au CKAN catalogue', the subject 'Australian open datasets', and the return value 'dataset metadata including resource URLs'. It also lists optional modifiers (Solr filter, sort, pagination), which makes the tool's scope unambiguous. The naming of the specific catalogue and the example filter distinguish it from generic search tools.

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 provides clear context on what the tool does and its optional parameters, implicitly indicating it is the primary dataset search tool. However, it does not explicitly state when to use this tool over alternatives (e.g., search_within or other sibling search tools), nor does it mention any exclusions or prerequisites. The usage guidance is adequate but relies on the agent to infer its place among 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
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