Skip to main content
Glama
rezmeplxrf

InsightSentry MCP

by rezmeplxrf

screen_etfs

Screen ETFs by exchange, country, and financial metrics. Filter exchange-traded funds to retrieve NAV, volume, pricing, and performance data with sorting and pagination.

Instructions

ETF Screener. Retrieve ETF data based on specified filter criteria → Returns {hasNext: boolean, current_page: number, total_page: number, current_items: number, data: [{symbol_code: string, name: string, country: string, currency: string, delay_seconds: number, ...requested_fields}]}. WORKFLOW: 1) Call get_etf_screener_params to discover available fields. 2) POST with your chosen fields. Example: {"fields":["close","volume","nav"],"exchanges":["NYSE","NASDAQ"],"countries":["US","CA"],"page":1,"sortBy":"nav","sortOrder":"desc"}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsYesArray of field names to include in the response (1-10 fields). Discover available fields by calling get_etf_screener_params first. Field names are case-insensitive.
exchangesNoArray of exchange names to filter by (e.g., ["NYSE", "NASDAQ"]). Discover available exchanges via the GET screener params tool.
ignore_invalidNoIf true, invalid fields, exchanges, or countries are silently filtered out instead of returning an error. Useful when you're unsure if a field exists.
countriesNoArray of country codes to filter by (e.g., ["US", "CA"]). Not available for crypto screener. Discover available countries via the GET screener params tool.
pageNoPage number for pagination
sortByNoField name to sort results by. Must be one of the requested fields or "name". Default: "name".
sortOrderNoSort order: "asc" (ascending) or "desc" (descending). Default: "asc".
filterNo(Optional) JSONata expression to filter/transform the API response server-side before it reaches you. Use this to extract only the fields or rows you need, reducing token usage. See https://jsonata.org for syntax.
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the complete return structure including pagination fields (hasNext, total_page) and data array contents, which compensates for the missing output_schema. It also establishes the two-step workflow constraint. Does not mention rate limits or caching, preventing 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?

Information-dense and well-structured: opens with purpose, documents return structure (necessary without output schema), provides workflow steps, and includes a concrete example. The inline JSON for return structure is lengthy but essential; no sentences are wasted.

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?

Comprehensive for an 8-parameter tool with no annotations or output schema. The description documents the return payload structure, pagination behavior, prerequisite workflow steps, and provides a complete usage example, fully addressing the complexity gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, establishing a baseline of 3. The description adds significant value with a concrete JSON example showing valid field values ('close', 'volume', 'nav'), exchange codes ('NYSE', 'NASDAQ'), and sort configuration, clarifying how parameters interact in practice.

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 clearly states the tool 'Retrieve[s] ETF data based on specified filter criteria'—specific verb, resource, and method. It explicitly identifies the domain as 'ETF Screener,' distinguishing it from sibling tools like screen_bonds, screen_crypto, and screen_stocks.

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

Usage Guidelines5/5

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

Provides explicit WORKFLOW with numbered steps: '1) Call get_etf_screener_params to discover available fields. 2) POST with your chosen fields.' This establishes the prerequisite dependency on get_etf_screener_params and the correct sequence of operations.

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/rezmeplxrf/insight_mcp'

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