NZXplorer (Remote)

get_esg_target_credibility

Read-onlyIdempotent

Assess the credibility of an NZX company's net zero and emissions reduction targets. Evaluates Scope 3 disclosure (materiality, trend, coverage), target credibility (7 factors: emissions trajectory, SBTi validation, timeline, baseline, multi-year data, intensity metrics, Scope 3 inclusion). Returns combined score (0-100), credibility rating (Strong/Moderate/Weak/No Target), sector materiality assessment, and key findings. Use when asked about climate targets, net zero credibility, Scope 3 emissions, or ESG target quality.

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

Input Schema

Name	Required	Description	Default
`ticker`	Yes	NZX ticker symbol (e.g. "FPH", "AIR", "SPK")

Output Schema

Name	Required	Description
`data`	Yes	The 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".
`meta`	Yes
`tool`	Yes	Tool that produced this result.
`schema_version`	Yes	Envelope contract version. Bumps only on a breaking shape change.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes beyond them by disclosing the internal method (7 named factors, Scope 3 materiality/trend/coverage), the 0-100 score scale and the four rating bands. It does not mention data recency, coverage limits, or any cost/latency characteristics, so it falls short of a 5.

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?

Three sentences, front-loaded with purpose, then method, then output and usage. The parenthetical factor list is dense but informative rather than filler. Slightly more enumeration than an agent strictly needs, which keeps it off a 5.

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?

An output schema exists and the description still briefly signals what comes back (score, rating, sector materiality, key findings), and together with purpose, method and usage triggers nothing an agent needs to call this correctly is missing. Complete for a single-parameter analytical tool.

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?

Only one parameter, ticker, and schema coverage is 100% with an example set ('FPH', 'AIR', 'SPK') already in the schema. The description adds no new meaning about the parameter, so the baseline 3 applies.

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 ('Assess the credibility of an NZX company's net zero and emissions reduction targets') and enumerates the seven credibility factors, so the tool's scope is unambiguous. However, it never names or contrasts the adjacent siblings an agent could confuse it with, notably get_climate_gap_analysis, get_greenwashing_detection and get_esg_disclosure_benchmark.

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 closing sentence gives concrete triggers: climate targets, net zero credibility, Scope 3 emissions, ESG target quality. That is a clear when-to-use signal, but there is no when-not-to-use and no routing to the neighbouring ESG/climate tools, so the agent must infer the boundary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All NZXplorer (Remote) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?