Skip to main content
Glama
mambaventures

NZXplorer MCP Server

screen_stocks

Screen NZX stocks by financial, governance, and technical metrics using presets or custom filters to find companies matching specific criteria.

Instructions

Screen NZX stocks using 87+ financial, governance, and technical metrics. Supports 12 smart presets (value, growth, quality, dividend_at_risk, insider_buying, capital_raise_likely, ceo_pay_for_failure, governance_laggards, oversold, overbought, golden_cross, below_200ma) and custom metric filters. Returns matching companies with selected columns, sorted by any metric. Use this to find stocks matching specific criteria like 'PE under 15 with dividend yield above 5%' or 'RSI below 30'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch by company name or ticker
sortNoSort by any column name (e.g. 'pe_ratio', 'market_cap', 'dividend_yield', 'rsi_14', 'grs_score')
limitNoNumber of results (default 50, max 130)
orderNoSort order (default 'asc')
filterNoCustom metric filters as comma-separated conditions. Format: metric>value,metric<value. Examples: 'pe_ratio<15,dividend_yield>3', 'rsi_14<30', 'roe>15,debt_to_equity<1'. Operators: >, <, >=, <=, =. Available metrics include: pe_ratio, pb_ratio, dividend_yield, roe, roa, net_margin, revenue_growth_yoy, debt_to_equity, current_ratio, rsi_14, price_vs_sma200_pct, grs_score, insider_conviction_score, dividend_safety_score, and 70+ more.
presetNoSmart preset filter. Each preset applies specific metric filters and shows relevant columns.
sectorNoFilter by sector (e.g. 'Energy', 'Healthcare', 'Property')
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It states the tool returns matching companies with selected columns and sorted, but does not disclose default columns, pagination behavior, rate limits, or error handling, leaving gaps in transparency.

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?

The description is three sentences that are front-loaded with the main action, includes a list of presets, and ends with usage examples. It is concise with no fluff, but could be slightly more structured for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (87 metrics, 7 optional parameters, no output schema), the description lacks details on output format, default columns, and parameter interactions (e.g., combining presets with custom filters). The limit parameter is mentioned but not how pagination works.

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% with each parameter already described; the description adds value by listing the 12 presets and giving usage examples, but does not detail preset meanings or how filters interact with presets, so it adds moderate additional meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states 'Screen NZX stocks' with specific verb and resource, and distinguishes from sibling tools by focusing on a 87+ metric screening capability with 12 unique smart presets, which no other sibling tool provides.

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?

The description advises 'Use this to find stocks matching specific criteria' with examples, but does not specify when not to use this tool or mention alternative tools like get_fair_value or get_technical_signals for similar screening tasks.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mambaventures/nzxplorer-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server