Skip to main content
Glama

NZXplorer (Remote)

subscribe_insider_alerts

Read-onlyIdempotent

Create an insider trading alert subscription. Monitors insider trades (director share transactions) for specified tickers and delivers notifications via email, webhook, Slack, or Teams. Supports filtering by minimum trade value and trade types (Buy, Sell, Exercise, Transfer). Use when asked to set up insider trade alerts, watch for director buying/selling, or monitor insider activity.

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": {
      "email_address": "<email_address>"
    },
    "name": "subscribe_insider_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFriendly name for this alert subscription (default: "Insider Trade Alerts")
tickersNoNZX ticker symbols to watch (e.g. ["AIR", "FPH"]). Empty array = all companies.
min_valueNoMinimum trade value in NZD to trigger alert (e.g. 10000)
trade_typesNoTrade types to watch: Buy, Sell, Exercise, Transfer, Other
email_addressYesEmail address for delivery (required if delivery_method is email)
delivery_methodNoDelivery method: email, webhook, slack, or teams (default: email)

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
Behavior1/5

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

The description describes creating a persistent subscription that 'delivers notifications via email, webhook, Slack, or Teams', which is a state-changing operation with external side effects, while the annotations declare readOnlyHint=true and destructiveHint=false. This is a direct contradiction of the supplied annotation profile, matching the annotation-contradiction case.

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?

Four sentences, front-loaded with purpose, then behavior, then filters, then usage triggers. Slightly redundant phrasing appears in 'Monitors insider trades (director share transactions)', but no sentence is wasted or buried out of order.

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?

With an output schema present and 100% parameter coverage, the description only needs to convey intent, scope, and delivery behavior, all of which it does. It also clarifies the empty-ticker 'all companies' semantics implicitly via scope and names the delivery channels, leaving no practical gap for invocation.

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 every parameter is already documented and the baseline is 3. The description echoes the key filters (minimum trade value, trade types Buy/Sell/Exercise/Transfer, delivery channels) but adds no syntax, format, or constraint detail beyond the schema, and it omits 'Other' from the trade types it lists.

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 names a specific verb and resource ('Create an insider trading alert subscription') and immediately scopes it to director insider trades on tickers, which is clearly distinguishable from the sibling subscribe_people_alerts. An agent can tell what this tool does without opening the schema.

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?

It gives explicit trigger conditions: 'Use when asked to set up insider trade alerts, watch for director buying/selling, or monitor insider activity.' That is strong positive routing guidance, but no exclusions or named alternatives (e.g. when to prefer subscribe_people_alerts or get_insider_trades), so it falls short of a 5.

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