Skip to main content
Glama

run_nz_companies_search

Search New Zealand's Companies Register by company name to retrieve registration numbers, status, addresses, and profile links for due diligence or business checks.

Instructions

Search the New Zealand company registry (Companies Register) by company name: name, registration number, status, address and link. 1 point per returned record.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>"
    },
    "name": "run_nz_companies_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoStatus. Options: active = Active, inactive = Inactive / dissolved
keywordYesCompany name. e.g. fonterra
max_itemsNoMax items (up to 250)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It does disclose a meaningful behavioral trait — '1 point per returned record' — which signals a cost/consumption model an agent would not otherwise know. However, it omits pagination behavior (relevant given start_page/max_items) and any auth or rate-limit context.

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?

A single tightly-packed sentence with the resource and return fields front-loaded, plus a short cost clause. Nothing is padded, though the return-field list and cost note read as two loosely joined fragments rather than a structured statement.

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?

For a 4-parameter search tool with full schema coverage and no output schema, the description compensates well by naming the fields returned and the cost model. The main gap is guidance on when to pick this over the detail/documents siblings, and how pagination interacts with the point cost.

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 100%, with each parameter (keyword, status enum, max_items cap, start_page) already documented in the schema, so the baseline is 3. 'By company name' merely restates the keyword parameter and adds no format or matching hints (partial vs exact) beyond the schema.

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 (Search) and resource (New Zealand company registry / Companies Register), and enumerates the fields returned (name, registration number, status, address, link). It is distinguishable from the detail sibling run_nz_companies and from run_nz_company_documents, but never explicitly contrasts itself with them.

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?

Implies usage via 'by company name', but gives no when-to-use guidance and never names the alternative (run_nz_companies for a single known entity, run_nz_company_documents for filings). The agent must infer routing from sibling names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools