Skip to main content
Glama

Data Govt Nz Recently Changed Packages

data_govt_nz_recently_changed_packages
Read-onlyIdempotent

New Zealand open data catalogue (data.govt.nz CKAN), datasets most recently created or updated, paginated by limit/offset. Use to monitor NZ government open data activity.

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_recently_changed_packages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYesRecently changed/updated datasets

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 the safety profile is fully covered by structured data. The description adds only that results are paginated and that the recency covers both creation and update, without disclosing ordering guarantees, result size caps, or rate/auth considerations. Adequate but thin beyond the annotations.

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 compact sentences, front-loaded with the resource identity and scope before the use case. No filler or repetition; slightly terse at the cost of the pagination detail that would have been useful.

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 values need not be explained, and the annotations carry the safety profile. Still, for a paginated listing tool with zero schema coverage on both parameters, the definition omits default page size, maximum limit, and sort order — details an agent needs to call it predictably.

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% and the description only says 'paginated by limit/offset', restating the parameter names without adding defaults, maximums, ranges, or what happens when both are omitted. With both parameters undocumented in the schema, the description was the only place to supply that meaning and it largely does not.

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 names the specific resource (data.govt.nz CKAN catalogue) and the precise slice of it (datasets most recently created or updated), which is a meaningful verb+resource statement. It falls short of a 5 because it never explicitly distinguishes itself from close siblings like package_list or package_search, leaving the agent to infer the difference from the modifier 'recently changed' alone.

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?

There is a stated use case — 'monitor NZ government open data activity' — which gives the agent a scenario for selection. However, it offers no when-not guidance and never names an alternative (e.g. package_search for keyword lookups or package_list for a full listing), so the routing decision is only implied.

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.