Skip to main content
Glama

Data Govt Nz Resource Show

data_govt_nz_resource_show
Read-onlyIdempotent

New Zealand open data catalogue (data.govt.nz CKAN), metadata for a single resource (file/download) by resource ID: URL, format, size, description, and last modified date.

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": "resource-12345"
    },
    "name": "data_govt_nz_resource_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
idNoResource ID
urlNoResource URL
nameNoResource name
formatNoResource format (e.g. CSV, JSON)
createdNoCreation timestamp
package_idNoParent dataset ID
descriptionNoResource description
last_modifiedNoLast modification timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds meaningful context beyond that: this returns metadata only, not the file or download itself, which prevents an agent from expecting file content.

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?

One tight sentence, front-loaded with the source and the operation, followed by the returned fields. No filler or redundancy.

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?

With an output schema present, return values need not be detailed further, and the description correctly frames this as a single-record metadata lookup. The only gap is behavior on unknown IDs and how to obtain a valid resource ID from the sibling list/search tools.

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 description coverage is 0%, so the single 'id' property is undocumented in the schema apart from an example value. The description partially compensates by identifying it as a resource ID (as opposed to a dataset or organization ID), but gives no format, case, or validation guidance.

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?

Names a specific verb+resource: metadata for a single resource (file/download) identified by resource ID, and enumerates the returned fields (URL, format, size, description, last modified). An agent can distinguish it from the sibling dataset-level package tools, though no sibling is named explicitly.

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 implied by the phrase 'by resource ID' — call it when you already know the resource identifier. There is no explicit statement of when to prefer this over package_show/package_search, nor any exclusion or prerequisite (e.g., resolve a dataset first to obtain resource IDs).

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.