Skip to main content
Glama

NZXplorer (Remote)

get_accounting_quality

Read-onlyIdempotent

Get accounting quality scores for an NZX company. Shows Beneish M-score (manipulation risk), Piotroski F-score (financial strength 0-9), Altman Z-score (bankruptcy risk), plus interest coverage and current ratio.

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

Input Schema

NameRequiredDescriptionDefault
yearNoYear or range (e.g. "2024" or "2020-2024")
limitNoMax results
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. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds metric meaning (what each score measures and the F-score's 0-9 scale), but says nothing about data periods, caching, or how scores are computed — useful context, but not rich behavioral disclosure.

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?

Two tight sentences with zero filler; the resource and its output metrics are front-loaded, so an agent can evaluate fit in one read.

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-value structure need not be explained. The description enumerates the metric set well, but for a tool sitting among many financial-analysis siblings it leaves the agent to infer scope differences (e.g., vs. get_financial_distress) on its own.

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 ticker, year (including year-range syntax), and limit are already documented in the schema. The description only implies the ticker is an NZX symbol and adds no format or range detail beyond the schema, making the baseline 3 appropriate.

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?

The description states a specific verb and resource ('Get accounting quality scores for an NZX company') and enumerates the exact metrics returned (Beneish M, Piotroski F, Altman Z, interest coverage, current ratio), so the agent knows precisely what this tool computes. However, it does nothing to distinguish itself from close siblings like get_financial_distress, get_earnings_quality, or get_insolvency_status, which also deal with distress/bankruptcy risk.

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?

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. With siblings such as get_financial_distress (Altman Z bankruptcy risk) and get_earnings_quality overlapping heavily, the absence of routing guidance is a real gap.

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