Skip to main content
Glama

NZXplorer (Remote)

get_peer_mentions

Read-onlyIdempotent

Get peer mentions for an NZX company — which other companies reference it in their announcements, and which companies it references. Extracted from NZX announcements. Shows network of business relationships, competitive dynamics, and sector interconnections. Includes context snippets. Each mention includes a relation_type (supplier, customer, partner, competitor, joint_venture, acquirer, subsidiary, licensee, advisor, shareholder, none) and relation_confidence (high, medium, low). Summary includes counts by relation type. Filter by relation type with the relation parameter.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_peer_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesNZX ticker symbol (e.g. "FPH", "AIR", "SPK")
relationNoFilter by relation type(s), comma-separated (e.g. "supplier,customer")
directionNoFilter direction: "mentions" (companies this ticker references), "mentioned_by" (companies referencing this ticker), or "both" (default)

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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: the extraction source (NZX announcements), the inclusion of context snippets, the relation_type and relation_confidence vocabulary, and that the response carries counts by relation type.

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 definition and the data source, then layered with return-field detail. The sentence about "network of business relationships, competitive dynamics, and sector interconnections" is the only mildly promotional filler; everything else carries information.

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 spelled out, and the description still covers source, mention semantics, relation vocabulary, and filtering. The only gap is the absence of usage routing against sibling relationship tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description goes further by enumerating the relation_type values (supplier, customer, partner, competitor, etc.) that the comma-separated relation filter accepts, which tells the agent valid filter inputs that the schema itself does not list.

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 (peer mentions for an NZX company) and pins the data source to NZX announcements, which implicitly distinguishes it from the many graph/network siblings. It never names an alternative sibling (get_company_connections, get_network_intelligence, get_corporate_relationships), so it stops short of full sibling differentiation.

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?

The description explains what data comes back and how to filter it, but gives no when-to-use guidance, no when-not-to-use guidance, and no routing to alternatives despite a large set of overlapping relationship/graph tools. The final sentence is parameter instruction, not usage context.

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