Skip to main content
Glama

Datagov Au

by io.github.pipeworx-io

Resource

resource
Read-onlyIdempotent

Single resource (downloadable file) by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoResource UUID
urlNoResource download URL
hashNoFile hash value
nameNoResource name
sizeNoFile size in bytes
formatNoFile format (e.g. CSV, JSON)
createdNoISO 8601 creation timestamp
package_idNoParent package UUID
descriptionNoResource description
last_modifiedNoISO 8601 modification timestamp

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: +[
+  {
+    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "created": {
+      "description": "ISO 8601 creation timestamp",
+      "type": "string"
+    },
+    "description": {
+      "description": "Resource description",
+      "type": "string"
+    },
+    "format": {
+      "description": "File format (e.g. CSV, JSON)",
+      "type": "string"
+    },
+    "hash": {
+      "description": "File hash value",
+      "type": "string"
+    },
+    "id": {
+      "description": "Resource UUID",
+      "type": "string"
+    },
+    "last_modified": {
+      "description": "ISO 8601 modification timestamp",
+      "type": "string"
+    },
+    "name": {
+      "description": "Resource name",
+      "type": "string"
+    },
+    "package_id": {
+      "description": "Parent package UUID",
+      "type": "string"
+    },
+    "size": {
+      "description": "File size in bytes",
+      "type": "number"
+    },
+    "url": {
+      "description": "Resource download URL",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that the resource is a downloadable file, but no further behavioral details such as error handling or response format are given.

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, front-loaded sentence with no wasted words, effectively communicating the tool's essence.

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 simple single-parameter tool with output schema and safety annotations, the description is largely sufficient. It lacks guidance on when to use versus alternatives, but the tool's simplicity lowers the need for extensive detail.

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?

With 0% schema description coverage, the description compensates minimally by stating 'by id', clarifying the purpose of the id parameter. The schema example provides a UUID format, but the description does not elaborate on id format or constraints beyond that.

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?

The description 'Single resource (downloadable file) by id' clearly identifies the tool as fetching a single resource by its identifier, distinguishing it from search/list tools. However, it lacks an explicit verb like 'get' or 'retrieve', making it slightly indirect but still specific.

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 implies usage when a known resource ID exists, but does not explicitly state when to use it over siblings like 'search' or 'recall'. No alternatives or exclusions are mentioned.

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