Skip to main content
Glama

Data Govt Nz Package List

data_govt_nz_package_list
Read-onlyIdempotent

New Zealand open data catalogue (data.govt.nz CKAN), paginated list of all dataset slugs/names. Use to enumerate available datasets before fetching details with package_show.

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": {
      "limit": 10,
      "offset": 0
    },
    "name": "data_govt_nz_package_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYesList of dataset names

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds that the listing is paginated and returns only slugs/names, which is genuinely useful for judging payload cost, but it doesn't state default or maximum page size, how large the catalogue is, or what happens when offset exceeds the total — the practical behaviors an agent paging this actually needs.

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?

Two sentences, zero filler, with the resource identification front-loaded and the follow-up instruction second. Efficient and easy to scan, though it would read slightly better with the pagination contract attached to the sentence that mentions paging.

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?

An output schema exists, so the description needn't explain return values, and the four rich annotations plus explicit cross-reference to package_show cover most of what an agent needs. What's missing is the concrete paging contract (defaults, caps) for a two-parameter list tool with no schema documentation on either parameter.

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 0% and both parameters (limit, offset) are undocumented in the schema, so the description carries the burden — it signals pagination, which explains why both params exist. However it supplies no defaults, no upper bound on limit, and no indication that offset must be a multiple of limit, so the meaning added beyond the parameter names is thin.

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?

States a specific verb and resource — a paginated list of dataset slugs/names from the data.govt.nz CKAN catalogue — and explicitly scopes what is returned (slugs/names, not full records). It also names package_show as the follow-up tool, so an agent can separate the enumeration step from the detail step without opening either schema.

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?

Gives explicit when-to-use guidance: enumerate datasets first, then fetch details with package_show. The gap is that it doesn't say when to prefer a targeted search (package_search, a sibling) over paging through every slug, so an agent may dump the whole catalogue when a filtered query would be cheaper.

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.