Skip to main content
Glama

NZXplorer (Remote)

get_property_climate_risk

Read-onlyIdempotent

Get climate and natural hazard risk analysis for an NZX property company portfolio. Returns per-property risk scores (0-100 composite), seismic zones (NZS 1170.5, 1-4), flood risk, liquefaction risk, coastal proximity, and sea level rise exposure. Includes portfolio-level averages, high-risk property count, and highest seismic zone. Based on published NZ government hazard data (NZS 1170.5, GNS Science, MfE, NIWA). Works for: KPG, ARG, PFI, VHP, IPL, SPG, CDI, GMT, PCT, APL.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_property_climate_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesNZX ticker symbol of a property company (e.g. "KPG", "GMT", "VHP")

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

A3.9/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 profile is covered. The description adds provenance the annotations cannot convey (NZS 1170.5, GNS Science, MfE, NIWA) and states that results include portfolio-level aggregates and a high-risk property count. It leaves the scoring methodology and any data-freshness or rate-limit behaviour unstated.

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?

Front-loads purpose, then output contents, then data provenance, then eligible tickers, in four compact sentences with no filler. Every clause carries information an agent can act on.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with annotations covering safety and an output schema covering return structure, the description supplies everything else needed: scope, metric definitions, aggregate contents, source data and the supported ticker universe.

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?

With a single parameter at 100% schema description coverage, the schema already defines ticker format and examples. The description's enumerated ticker list ('Works for: KPG, ARG, ...') adds genuine valid-value meaning, but the baseline of 3 for fully covered schemas is the right anchor since no additional argument semantics are offered.

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?

Names a specific verb (get) and a precise resource (climate and natural hazard risk analysis for an NZX property company portfolio), then enumerates the exact outputs: per-property scores 0-100, NZS 1170.5 seismic zones, flood, liquefaction, coastal proximity and sea level rise exposure. It does not reference the sibling get_climate_gap_analysis, so the boundary between the two climate tools is left implicit.

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 eligible universe is stated explicitly ('Works for: KPG, ARG, PFI, VHP, IPL, SPG, CDI, GMT, PCT, APL'), which tells an agent when the tool applies. However, there is no guidance on when to prefer this over get_climate_gap_analysis or get_property_portfolio, and no exclusion conditions or prerequisites beyond the ticker list.

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