Skip to main content
Glama

NZXplorer (Remote)

check_governance_policy

Read-onlyIdempotent

Run a governance policy compliance check across all NZX companies (or a subset). Evaluates board independence, gender diversity, director tenure, board size, non-exec chair, attendance, GRS score, auditor independence, committee structure, and financial health against configurable thresholds. 8 presets available (nzxplorer, conservative, progressive, market-friendly, iss-nz, nz-super, russell-nz, vanguard-aunz). Returns per-company pass/fail with rule breakdown and aggregate compliance statistics. Use when asked about governance compliance, policy screening, institutional governance standards, or market-wide governance scanning.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_governance_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetNoPolicy preset ID (default: "nzxplorer"). Options: nzxplorer, conservative, progressive, market-friendly, iss-nz, nz-super, russell-nz, vanguard-aunz
tickersNoComma-separated ticker list to check (default: all NZX companies)

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool payload. Null when the call did not produce one — read meta.availability_status to find out why, and do not treat null as zero, empty or "none found".
metaYes
toolYesTool that produced this result.
schema_versionYesEnvelope contract version. Bumps only on a breaking shape change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / meta / properties / provenance / description
      Previous value: -"Whether the figures can cite a source document. \"undeclared\" means no claim has been made for this endpoint yet — it is not a claim that the data is unsourced."New value: +"Whether the figures can cite a source document. \"direct\": every returned row carries its own document URL (see meta.sources). \"reachable\": some do, or the documents sit beside figures that are not rows. \"undeclared\": no document URL was found in this payload — it is not a claim that the data is unsourced."
    • addedOutput schema / properties / meta / properties / sources
      Added value: +{
      +  "description": "Primary documents (NZX announcements, annual reports) whose URLs appear in this payload. Cite these with their date when you quote a figure. A listed document was returned with the data; it is not proof that a given sentence of your answer came from it.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "date": {
      +        "description": "YYYY-MM-DD, or null when the row has no date.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "kind": {
      +        "enum": [
      +          "announcement",
      +          "annual_report",
      +          "document"
      +        ],
      +        "type": "string"
      +      },
      +      "title": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "format": "uri",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "url",
      +      "title",
      +      "date",
      +      "kind"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  2. First observed

TDQS

A4.1/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 closed-world, so the safety burden is light; the description still adds useful behavior: eight named presets and the per-company pass/fail plus aggregate statistics return shape. One gap: it says thresholds are "configurable" but no threshold parameter exists, only presets, which could mislead an agent into hunting for a tuning argument.

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?

Front-loaded with the action and scope, then the evaluated dimensions, then return shape, then when-to-use – a sensible order. The mid-sentence list of ten rule dimensions is long but each item is informative; some compression into categories would tighten it.

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?

Given an output schema exists, the brief return-value sentence is sufficient, and both parameters are covered by schema plus description. Completeness is solid for a two-param read tool; only the alternative-tool routing and the "configurable thresholds" ambiguity are unaddressed.

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 coverage is 100% and the schema already lists the eight preset IDs and the all-companies default, so the description adds little parameter meaning beyond it. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose5/5

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

States a specific verb and resource ("Run a governance policy compliance check") plus explicit scope (all NZX companies or a subset), and enumerates the ten rule dimensions evaluated. An agent can distinguish this from siblings like get_governance_scorecard or get_governance_deterioration purely from the description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use when asked about governance compliance, policy screening, institutional governance standards, or market-wide governance scanning" gives concrete triggering contexts. It does not, however, name when to prefer this over the sibling scorecard/score/deterioration tools, nor when not to use it, so routing between similar governance tools still requires inference.

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.

Resources