Skip to main content
Glama

Data Govt Nz Group Show

data_govt_nz_group_show
Read-onlyIdempotent

New Zealand open data catalogue (data.govt.nz CKAN), full detail for a thematic group by ID: title, description, and optionally the datasets it contains.

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": "economy"
    },
    "name": "data_govt_nz_group_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
include_datasetsNo

Output Schema

NameRequiredDescriptionDefault
idNoGroup ID
nameNoGroup name
titleNoGroup title
datasetsNoGroup datasets if include_datasets=true
descriptionNoGroup description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already disclose read-only, idempotent, non-destructive and open-world behavior, so the description only needs to add context. It does add that detail includes title/description and that contained datasets are conditional, but says nothing about what happens with an unknown ID, whether include_datasets defaults on, or result size.

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?

A single dense sentence, front-loaded with the catalogue identity and the verb, followed by the resource and 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, the description needn't describe return values, and rich annotations handle the safety profile. For a two-parameter read tool this is nearly complete; the only shortfall is the absent default for include_datasets and no error/edge-case behavior.

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 a thematic group and that include_datasets controls whether contained datasets are returned, but gives no ID format guidance, no default for the boolean, and no indication of the output shape when datasets are excluded.

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+resource: 'full detail for a thematic group by ID', and enumerates the returned fields (title, description, optionally datasets). It implicitly contrasts with the group_list sibling by saying 'full detail ... by ID', though it never names that sibling.

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 only implied: fetch one group's detail when you have its ID, and opt into datasets via a flag. No explicit when-to-use/when-not, no named alternatives (e.g. group_list for enumeration, package_show for a dataset), and no prerequisites 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.