Skip to main content
Glama

Data Govt Nz Package Search

data_govt_nz_package_search
Read-onlyIdempotent

Full-text + faceted search.

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": {
      "q": "housing"
    },
    "name": "data_govt_nz_package_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
fqNo
rowsNo
sortNo
startNo
facet_fieldNo

Output Schema

NameRequiredDescriptionDefault
countNoTotal number of matching datasets
facetsNoFaceted search results
resultsNoSearch result datasets

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, so safety is covered externally. The description adds nothing beyond that — no mention of pagination, ranking behavior, or how faceting results are returned, which matters for a search tool with open-world scope.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short phrase is concise in length but not in effect; it is under-specified rather than efficient. Nothing is front-loaded beyond a generic mode label, and no sentence earns its place by informing the caller.

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

Completeness2/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, but six undocumented parameters with zero usage guidance leave the caller without enough information to invoke the tool correctly. For a search entry point in a large sibling set, this is well short of adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters (q, fq, rows, start, sort, facet_field), so the description carries the full burden — and it documents none of them. It does not explain query syntax, the fq filter format, sort direction, or how facet_field changes the response.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'Full-text + faceted search' restates what the tool name (package_search) already implies and never names the resource being searched. It gives a vague mode of operation but no object, so an agent cannot tell it apart from siblings like data_govt_nz_package_list or data_govt_nz_package_show other than by guessing from the name.

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 when-to-use, when-not-to-use, or alternative routing. An agent has no signal on why it should call this instead of package_list or search_within; the entire decision is left to inference from the tool name.

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.