Skip to main content
Glama
rezmeplxrf

InsightSentry MCP

by rezmeplxrf

screen_stocks

Filter stocks by exchange, country, and financial metrics to identify securities matching your criteria. Retrieve customizable market data for NYSE, NASDAQ, and global equities.

Instructions

Stock Screener. Retrieve stock 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_stock_screener_params to discover available fields, exchanges, countries. 2) POST with your chosen fields. Tip: Filter by exchanges (e.g., ["NYSE", "NASDAQ"]) to exclude OTC/penny stocks. Example: {"fields":["close","volume","market_cap"],"exchanges":["NYSE","NASDAQ"],"countries":["US","CA"],"page":1,"ignore_invalid":false,"sortBy":"market_cap","sortOrder":"desc"}. Returns up to 1000 results per page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsYesArray of field names to include in the response (1-10 fields). Discover available fields by calling the GET screener params tool first (e.g., get_stock_screener_params). 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, description carries full burden and discloses return structure (hasNext, current_page, data array), pagination limits (1000 results/page), and response fields (delay_seconds). Missing explicit rate limits or error scenarios beyond ignore_invalid behavior.

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?

Efficiently structured with purpose first, followed by return type arrow notation, workflow steps, pro tip, and example. Every sentence serves distinct purpose (workflow, filtering advice, pagination limits). No redundancy despite high information density.

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 8-parameter tool with no output schema. Documents return structure, pagination behavior, prerequisite discovery tool, and includes working example. Compensates fully for lack of annotations and output schema.

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% so baseline is 3. Description adds value with concrete JSON example showing realistic field values (NYSE, NASDAQ, market_cap) and practical tip about excluding penny stocks, enhancing semantic understanding of exchanges parameter.

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?

Explicitly states 'Stock Screener' with specific verb 'Retrieve stock data'. Clearly distinguishes from siblings (screen_bonds, screen_crypto, screen_etfs) by specifying 'stock' and referencing get_stock_screener_params for discovery.

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 naming the prerequisite sibling tool (get_stock_screener_params). Includes practical 'Tip' on using exchanges parameter to exclude OTC/penny stocks, giving clear when-to-use guidance.

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