Skip to main content
Glama

Datagov Au

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Groups

groups
Read-onlyIdempotent

List all thematic groups (topic categories) in the data.gov.au CKAN catalogue with names and slugs; useful for discovering available subject-area filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYesList of themes (groups/categories)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 50
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "description": "List of themes (groups/categories)",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Group description",
+            "type": "string"
+          },
+          "id": {
+            "description": "Group UUID",
+            "type": "string"
+          },
+          "image_url": {
+            "description": "Group image URL",
+            "type": "string"
+          },
+          "name": {
+            "description": "Group name/slug",
+            "type": "string"
+          },
+          "package_count": {
+            "description": "Number of packages in group",
+            "type": "number"
+          },
+          "title": {
+            "description": "Group display title",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds useful context about the resource and output fields (names and slugs), but does not detail behavior like pagination or response structure. With annotations covering safety, this is adequate but not rich.

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 sentence that front-loads the action ('List all') and includes the resource, output fields, and a practical use case. No unnecessary words or repetition.

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?

Given the presence of an output schema and strong annotations, the description covers the core purpose and output contents. However, it omits an explanation of the 'limit' parameter and does not reference sibling tools like 'tags' or 'organizations' for alternative facets, leaving minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter, 'limit', is not explained in the description, and the schema has 0% description coverage. The description does not compensate by clarifying how the limit affects results, leaving the agent without explicit guidance on this parameter.

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 a specific verb ('List') and resource ('thematic groups in the data.gov.au CKAN catalogue'), and specifies the output (names and slugs). It also distinguishes from sibling tools like 'tags' and 'organizations' by describing groups as topic categories and subject-area filters.

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 provides clear context on when to use the tool ('useful for discovering available subject-area filters'), but it does not explicitly mention alternatives or exclude cases. This aligns with 'clear context, no exclusions'.

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