Skip to main content
Glama

Data Govt Nz Group List

data_govt_nz_group_list
Read-onlyIdempotent

New Zealand open data catalogue (data.govt.nz CKAN), list thematic groups/categories used to organise NZ open datasets. Pass all_fields=true for names and descriptions.

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": 20
    },
    "name": "data_govt_nz_group_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
all_fieldsNo

Output Schema

NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYesList of groups/categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 the safety profile is covered. The description adds that all_fields controls whether descriptions come back, which is useful output-shaping context, but says nothing about pagination, default result counts, or total-count behavior despite limit/offset existing.

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?

Two tight sentences: catalogue identity first, then the one high-value flag hint. No filler, no restatement of the title, and the most decision-relevant information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-shape explanation is not required, and the CKAN provenance is helpful. However, for a paginated list tool with zero schema descriptions, the absence of any note on paging or defaults leaves an agent under-informed about how to enumerate the full set of groups.

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?

Schema description coverage is 0%, so the description must carry the burden, and it only explains one of three parameters (all_fields yields names plus descriptions). The meaning, defaults, and interaction of limit and offset are left entirely undocumented.

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 specific verb and resource: lists thematic groups/categories in the data.govt.nz CKAN catalogue, and clarifies these organise NZ open datasets. This distinguishes it reasonably from tag_list/organization_list/package_list siblings by resource type, though it never names them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance; the only actionable instruction concerns the all_fields flag, which is a parameter hint rather than routing guidance. An agent must infer that this tool is the choice when group/category names are wanted instead of tags, organisations, or packages.

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.