nzxplorer-mcp

get_capital_raises

Read-onlyIdempotent

Get capital raise history for an NZX company. Includes placements, rights issues, SPPs, IPOs, bonds, buybacks, DRPs with amounts, pricing, and dilution. Structured events across NZX issuers.

Input Schema

Name	Required	Description
`type`	No	Comma-separated raise types: placement, rights_issue, spp, ipo, bond, buyback, drp, options_exercise, employee_scheme, conversion
`year`	No	Year or range (e.g. "2024" or "2020-2024")
`limit`	No	Max results
`ticker`	Yes	NZX ticker symbol (e.g. "AIR", "FBU", "RYM")
`buybacks`	No	Set to "true" to only show buybacks

Output Schema

Name	Required	Description
`data`	Yes	The 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".
`meta`	Yes
`tool`	Yes	Tool that produced this result.
`schema_version`	Yes	Envelope contract version. Bumps only on a breaking shape change.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 16, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "The 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\"."
+    },
+    "meta": {
+      "additionalProperties": true,
+      "properties": {
+        "availability_status": {
+          "description": "ok: complete payload. truncated: payload exceeded the transport cap and was cut. parse_failed: payload is text this server could not parse as JSON. error: the tool raised.",
+          "enum": [
+            "ok",
+            "truncated",
+            "parse_failed",
+            "error"
+          ],
+          "type": "string"
+        },
+        "encoding": {
+          "description": "toon = pipe-delimited tabular encoding; header row names the columns.",
+          "enum": [
+            "json",
+            "toon"
+          ],
+          "type": "string"
+        },
+        "provenance": {
+          "description": "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.",
+          "enum": [
+            "direct",
+            "label",
+            "reachable",
+            "none",
+            "undeclared"
+          ],
+          "type": "string"
+        },
+        "retrieved_at": {
+          "description": "When this platform produced the answer — NOT the as-at date of the data.",
+          "format": "date-time",
+          "type": "string"
+        },
+        "warnings": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "retrieved_at",
+        "availability_status",
+        "provenance"
+      ],
+      "type": "object"
+    },
+    "schema_version": {
+      "description": "Envelope contract version. Bumps only on a breaking shape change.",
+      "type": "string"
+    },
+    "tool": {
+      "description": "Tool that produced this result.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "schema_version",
+    "tool",
+    "data",
+    "meta"
+  ],
+  "type": "object"
+}

First observedJun 12, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes some value by specifying the breadth and structure of returned events (amounts, pricing, dilution), but says nothing about permissions, data currency, coverage gaps, or result limits beyond what the schema states.

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?

Two tight sentences, front-loaded with the core verb+resource and then the payload contents. The closing clause 'Structured events across NZX issuers' is mildly redundant given 'NZX company' already appears, but overall there is little waste.

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?

An output schema exists so return values need not be explained, and all five parameters are fully documented in the schema. The description covers scope (NZX issuers) and content classes, which is adequate; only cross-tool routing and edge cases (e.g., no raises found, date-range behavior) 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 description coverage is 100%, so the schema already documents ticker, type, year, limit, and buybacks. The description's list of raise types loosely mirrors the type parameter's allowed values but adds no syntax, format, or interaction detail (e.g., how 'buybacks' overlaps with type=buyback). Baseline 3 applies when the schema carries the parameter burden.

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 ('Get capital raise history') and enumerates the event classes it returns (placements, rights issues, SPPs, IPOs, bonds, buybacks, DRPs), which distinguishes it from generic financial tools like get_financials or get_dividends. It does not, however, explicitly distinguish itself from the closely named sibling get_capital_raise_sentiment, which is the tool most likely to be confused with it.

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 guidance on when to use this tool versus alternatives such as get_capital_raise_sentiment, get_takeovers, or get_dividends. Usage is only implied by the data types listed; no prerequisites, exclusions, or routing hints are provided.

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

All nzxplorer-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.