Skip to main content
Glama

NZXplorer (Remote)

simulate_investor_qa

Read-onlyIdempotent

Generate 10 tough investor questions for an NZX company with data-backed suggested responses. Simulates the hardest questions IR teams will face on investor calls or roadshows. Uses earnings intelligence, management credibility, peer comparison, insider activity, governance, and sentiment data. Categories: financial_performance, governance, strategy, capital_allocation, risk, valuation, insider_activity, guidance, peer_comparison, esg. Each question rated by difficulty (standard/tough/hostile) and risk level. ~$0.01-0.03/call.

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

Input Schema

NameRequiredDescriptionDefault
tickerYesNZX ticker symbol (e.g. "FPH", "AIR", "SPK")

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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the description is free to add operationally useful context instead: a fixed count of 10 questions, the specific data sources consulted, the enumerated categories, the difficulty/risk ratings on each item, and a per-call cost of ~$0.01-0.03. Cost disclosure is genuinely valuable for an agent deciding whether to invoke. What is missing is whether the data sources must be current, any latency expectation, or how sources are cited in responses.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the deliverable and count, then supporting detail in descending importance: purpose, data sources, categories, rating scheme, cost. Every clause carries information an agent can act on, and the category list, while long, is the only place this taxonomy appears.

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 shape need not be re-explained, and the description nevertheless previews question attributes (difficulty, risk level). Input side is trivial and fully covered by schema. The only gap left relative to complexity is the absence of any qualifier on how current or reliable the underlying intelligence must be.

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% and the single parameter already documents the NZX ticker with examples ("FPH", "AIR", "SPK"). The description adds nothing about ticker handling, so there is no meaning to add beyond the schema. Baseline 3 is correct.

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 concrete verb and artifact: "Generate 10 tough investor questions for an NZX company with data-backed suggested responses," plus the scenario (investor calls/roadshows). An agent can tell this produces Q&A prep material rather than raw research or event simulation. It stops short of naming the closest sibling (get_deep_research_qa) or explaining how this differs from simulate_event, so differentiation is by description only.

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

Usage Guidelines3/5

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

Usage context is implied through "IR teams will face on investor calls or roadshows," which tells the agent the situation but not the decision rule. There is no explicit when-not guidance, no prerequisite (e.g. whether an annual report or prior analysis must exist), and no comparison to sibling tools. Adequate but leaves the agent to infer selection.

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