Skip to main content
Glama

NZXplorer (Remote)

get_anomalies

Read-onlyIdempotent

Get market anomaly detection results — an early warning system scanning all NZX companies for unusual patterns. Detects 16 anomaly types across 7 categories: insider trading clusters, insider exodus, conviction shifts, governance deterioration, director exodus, audit changes, dividend cut risk, capital raise patterns, earnings concerns, first-time risk language detection, technical breakdowns/breakouts, AGM revolts, active takeovers, sentiment-market disagreements, and buried risk detection. Use this when asked about "red flags", "warning signs", "anomalies", "governance concerns across the market", "which companies have problems", "sentiment disagreement", "buried risks", or market-wide risk assessment.

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_anomalies"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to look back (default 180)
sectorNoFilter by sector (e.g. "Energy", "Healthcare")
tickerNoFilter by company ticker (e.g. "AIR", "MEL")
categoryNoFilter by category: insider, governance, financial, market, agm
severityNoFilter by severity: critical, warning, watch

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. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and scope (openWorldHint false), so the description adds useful behavioral context by explaining that it scans all NZX companies and detects 16 specific anomaly types. It does not describe output format or pagination, but the presence of an output schema reduces the need for that.

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 purpose and then lists anomaly types, followed by usage guidance. While the list of 16 anomaly types is long, it is necessary to convey the tool's breadth; there is little waste, though the sentence structure could be slightly tighter.

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?

Given the tool's complexity (broad market scanning), the description is complete enough: it explains what it does, when to use it, and what it detects. The presence of annotations and an output schema means the description does not need to cover safety or return values, and the schema handles parameters fully.

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?

The input schema has 100% description coverage, so parameters are already well-documented (days, sector, ticker, category, severity). The description adds no parameter-specific semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 clearly states the tool's purpose with a specific verb (Get) and resource (market anomaly detection results), and elaborates by listing 16 anomaly types across 7 categories. It distinguishes itself as a broad, market-wide early warning system scanning all NZX companies, implicitly contrasting with more focused sibling tools like get_governance_deterioration or get_insider_clusters.

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?

The description provides explicit trigger phrases (e.g., 'red flags', 'warning signs', 'anomalies') and contexts like 'market-wide risk assessment', clearly indicating when to use this tool. However, it does not explicitly mention when NOT to use it or name alternative sibling tools for narrower queries, which prevents a perfect score.

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