Skip to main content
Glama

nzxplorer-mcp

by io.github.mambaventures
OverviewDiscussionsAdmin

get_market_signals

Read-onlyIdempotent

Get the Market Intelligence Feed — a unified stream of all NZX market events. Returns 13 signal types: insider trades, capital raises, dividends, earnings releases, AGM results, director changes, governance score changes, technical signals (golden/death cross, RSI extremes), credit rating changes, auditor changes, takeover/M&A activity, board events, and composite signals (multi-signal patterns like insider selling + earnings miss, director exodus, governance deterioration). Use this when asked "what happened on the NZX today/this week?", "any recent insider trades?", "golden crosses?", "credit rating changes?", "composite signals?", "market activity for AIR", or any question about recent NZX events. ROUTING: this is the CROSS-MARKET FEED — use it for 'what is happening across the market' or when scanning several signal types at once. For a question about ONE dataset for ONE company, prefer the specific tool: get_capital_raises, get_agm_resolutions, get_vote_history, get_credit_ratings, get_audit_history, get_governance_scores, get_dividends, get_insider_trades. Listing a signal type here does NOT mean this is the best tool for it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of days to look back (default 180, use 7 for "this week", 1 for "today")
typeNoComma-separated signal types: insider_trade, capital_raise, dividend, earnings, agm_result, director_change, grs_change, technical_signal, credit_rating, audit_change, takeover, board_event, composite_signal
limitNoMax results (default 50)
sectorNoFilter by sector (e.g. "Energy", "Healthcare")
tickerNoFilter by company ticker (e.g. "AIR", "MEL")
significanceNoFilter by significance: high, medium, low

Output Schema

TableJSON 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. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / days / minimum
      Added value: +1
    • changedInput schema / properties / days / type
      Previous value: -"number"New value: +"integer"
    • 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"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar for added behavioral context is lower. The description adds meaningful behavior: it returns a unified cross-market stream, can combine multiple signal types, and includes composite signals that detect patterns like insider selling plus earnings miss. It also clarifies the feed's broad scope, which is not inferable from the schema alone.

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?

The description is front-loaded with the core definition and scope, then gives compact example queries and routing. It is longer than average, but the length is justified by the large palette of signal types and the need to distinguish siblings. The final caution about routing is somewhat redundant with the earlier routing statement but earns its place by preventing misuse.

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 six-parameter, no-required-parameter tool with an output schema, the description plus schema covers what an agent needs: purpose, scope, routing, parameter semantics, and return coverage via the output schema. It explicitly handles the common confusion with sibling tools and provides example invocations. No critical behavior or parameter concern is left 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% and each parameter (days, type, limit, sector, ticker, significance) already has a semantic description with defaults and examples. The tool description doesn't need to repeat parameter details, so the baseline of 3 applies. It does reinforce the available signal type vocabulary informally, but the schema already lists the exact underscore codes.

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?

The description opens with a specific verb and resource ('Get the Market Intelligence Feed') and immediately defines its scope as a unified stream of all NZX market events. It differentiates itself from sibling tools by explicitly stating it is the cross-market feed and by naming the specific single-dataset tools it is not. The enumeration of 13 signal types leaves no ambiguity about what the tool covers.

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

Usage Guidelines5/5

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

Contains explicit routing guidance: use it for 'what is happening across the market' or when scanning several signal types at once, and avoid it for a question about one dataset for one company. It names the preferred sibling tools for single-dataset queries (get_capital_raises, get_agm_resolutions, etc.) and adds the warning that listing a signal type does not mean this is the best tool. Example phrasings ('what happened on the NZX today/this week?') anchor when to use it.

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

All nzxplorer-mcp toolsInspect
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.

Resources