Skip to main content
Glama

Data Govt Nz Organization Show

data_govt_nz_organization_show
Read-onlyIdempotent

New Zealand open data catalogue (data.govt.nz CKAN), full profile for a publishing organization by ID: name, description, and optionally their list of published datasets.

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": "stats-nz"
    },
    "name": "data_govt_nz_organization_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
include_datasetsNo

Output Schema

NameRequiredDescriptionDefault
idNoOrganization ID
nameNoOrganization name
titleNoOrganization title
datasetsNoOrganization datasets if include_datasets=true
descriptionNoOrganization description

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?

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description need not repeat safety details. It adds useful context by identifying the CKAN catalogue and specifying that the profile includes name, description, and an optional list of published datasets. It does not describe error behavior for an unknown ID or any limits on the dataset list, but those gaps are modest given the annotations and output schema.

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?

The definition is a single front-loaded sentence that identifies the catalogue, the operation, the resource, and the optional data inclusion. Every phrase contributes useful information, with no repetition or filler.

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?

This is a low-complexity read-only show tool with two parameters, an output schema, and rich annotations. The description covers the core purpose, the returned profile fields, and the optional dataset list. It omits explicit sibling routing and parameter edge cases, but those are minor for an agent that already has the schema and output definition.

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 description must carry parameter meaning. It clarifies that id identifies the publishing organization and that include_datasets optionally adds the organization's published datasets, which is meaningful guidance beyond the bare schema. It does not specify the ID format, whether include_datasets defaults to false, or any listing limits, so it only partially compensates for the lack of schema descriptions.

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 states a specific verb and resource: it returns a full organization profile by ID from the New Zealand data.govt.nz CKAN catalogue. It also names the included fields and the optional dataset list, which makes its purpose clear. It does not explicitly differentiate itself from sibling tools such as organization_list or group_show, but the by-ID profile scope is distinguishable.

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?

The phrase 'by ID' implies the tool should be used when the organization identifier is already known, and 'optionally their list of published datasets' indicates when to set include_datasets. However, there is no explicit guidance on when to choose this over organization_list or other show tools, and no exclusions or prerequisites are stated.

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.