Skip to main content
Glama

NZXplorer (Remote)

get_volume_anomalies

Read-onlyIdempotent

Get volume anomaly detection for NZX stocks. Uses z-score analysis on daily OHLCV data to identify three types of unusual volume: spikes (single day z-score > threshold), clusters (3+ days of >2x avg volume in 7-day window), and price-volume divergences (big volume + small price move). Cross-references announcements within 5 trading days. Especially valuable on the thin NZX market where even modest institutional flows create detectable anomalies. Use when the user asks about unusual volume, trading activity, accumulation, distribution, or pre-announcement patterns.

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": "get_volume_anomalies"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to scan (default: 30, max: 365)
tickerNoOptional NZX ticker symbol to filter (e.g. "FPH"). Omit for all tickers.
min_zscoreNoMinimum z-score threshold (default: 2.0)

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds genuinely useful method detail (z-score, 3+ days of 2x average volume in a 7-day window, cross-referencing announcements within 5 trading days) that explains how results are derived. It says nothing about scan cost, result volume on the whole market, or what 'cross-references announcements' does to the output shape, leaving the agent without cost or latency expectations.

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 core verb and resource, then detection logic, then use cases, which is a sensible ordering. The sentence on thin NZX market and institutional flows is persuasive framing that consumes space without changing how the agent calls the tool, which keeps it from a 5.

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 and annotations are rich, so the description need not explain return values, and it correctly spends its budget on detection methodology and trigger phrasing instead. The main remaining gap for a multi-mode detection tool is that it never says whether results are grouped per anomaly type or per ticker, which affects how the agent should present them.

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% with defaults and a max documented for days, so the schema carries the parameter burden. The description supplies interpretive context for the z-score idea and the fixed 7-day/2x cluster rule, but it never ties these to min_zscore, days, or the ticker filter, and the 5-trading-day announcement window is not exposed as a parameter at all. Baseline 3 applies when schema coverage is complete and description adds only conceptual gloss.

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 and resource ('Get volume anomaly detection for NZX stocks') and enumerates the three anomaly classes it returns (spikes, clusters, price-volume divergences). A sibling named get_anomalies exists, and the description never clarifies how this volume-specific tool differs, so the agent must infer the distinction from the name.

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?

Closes with an explicit when-to-use list: 'unusual volume, trading activity, accumulation, distribution, or pre-announcement patterns', which maps user phrasing onto the tool. No exclusions or named alternative tools are given, and the relationship to get_anomalies is left unstated.

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