Skip to main content
Glama

Data Govt Nz Package Show

data_govt_nz_package_show
Read-onlyIdempotent

New Zealand open data catalogue (data.govt.nz CKAN), full metadata for a dataset by ID/slug: title, description, resources (download URLs + formats), organization, tags, and license.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "nz-population-census"
    },
    "name": "data_govt_nz_package_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
idNoDataset ID
nameNoDataset name
tagsNoAssociated tags
notesNoDataset description
titleNoDataset title
authorNoDataset author
groupsNoAssociated groups
resourcesNoDataset resources
organizationNoPublishing organization details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and idempotency are covered without help. The description adds scope (which metadata fields are returned) but says nothing about behavior on an unknown/ambiguous ID, whether a partial match is resolved, or rate limits — the gaps that matter for an open-world remote lookup.

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?

One sentence, front-loaded with the catalogue identity and then the payload contents; no filler or hedging. The field enumeration is slightly list-heavy and partially duplicates what the output schema already declares, but it stays readable.

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 one-parameter read-only lookup with an output schema present, this is close to complete: source, identifier form, and returned metadata are all stated, and return structure is the output schema's job. The only real omission is how it behaves when the identifier is wrong or ambiguous.

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 coverage is 0% — the single 'id' property is a bare string with no description — so the description carries the load. Saying 'by ID/slug' is genuinely useful: it tells the agent that a human-readable CKAN name works as well as a UUID, which the schema alone does not convey, and the schema example reinforces this.

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?

States a concrete verb-like action (fetch full metadata) on a specific resource (a data.govt.nz CKAN dataset) and enumerates what comes back: title, description, resources with URLs/formats, organization, tags, license. The 'by ID/slug' qualifier implicitly separates it from the list/search siblings, though it never names them.

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?

Usage is only implied: you need an identifier to call it, so it is the follow-up to a search/list. There is no explicit 'use this when you already have an ID, use package_search when you do not' routing, and no sibling is named, so the agent must infer the relationship.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.