Skip to main content
Glama

NZXplorer (Remote)

get_esg_disclosure_gap

Read-onlyIdempotent

Get multi-framework ESG disclosure gap analysis for an NZX company. Compares against three international standards: TCFD (11 recommendations), ISSB/IFRS S2 (climate disclosure requirements), and NZ XRB Climate Standards (NZ CS 1–3). Returns per-framework scores, requirement-level gaps with evidence and recommendations, mandatory reporter status, and overall multi-framework readiness score. Use when the user asks about ESG gaps, disclosure readiness, TCFD compliance, ISSB alignment, or multi-framework comparison.

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

Input Schema

NameRequiredDescriptionDefault
tickerYesNZX ticker symbol (e.g. "MEL", "CEN", "AIR")
frameworkNoFilter to a specific framework (default: all)

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

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral detail beyond that: it enumerates the returned artifacts (per-framework scores, requirement-level gaps with evidence and recommendations, mandatory reporter status, readiness score). No auth, rate-limit or cost caveats are given.

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 action, then scope, then return contents, then usage triggers — nothing is buried. The middle sentence is a long enumerated list that could be tightened, but every clause carries information rather than filler.

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, return-value explanation is optional, yet the description still summarises the shape of the response. Combined with annotations covering safety and 100% schema coverage on a two-parameter tool, an agent has everything needed to select and invoke this correctly.

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%: both the ticker format and the framework enum are fully documented in the schema. The description names the three frameworks but does not explain the 'all' default or what filtering to a single framework changes in the output, so it adds little beyond the schema baseline.

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 ('Get multi-framework ESG disclosure gap analysis') and pins the scope to an NZX company, naming the three standards it compares against. It is clear on its own, but with near-neighbours like get_climate_gap_analysis, get_esg_disclosure_benchmark and get_esg_data in the sibling set, it never distinguishes itself from those alternatives.

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 final sentence gives explicit invocation triggers ('ESG gaps, disclosure readiness, TCFD compliance, ISSB alignment, or multi-framework comparison'), which is solid when-to-use guidance. There are no when-not conditions and no routing to the overlapping ESG/climate siblings, so it stops 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