Skip to main content
Glama
myfinancialria

MyFinancial Market Data MCP

by myfinancialria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Stock Screener (Fundamental)

screen_stocks
Read-onlyIdempotent

Screen Indian stocks by fundamental criteria such as valuation, profitability, growth, and cash flow using 326 financial ratios. Filter with operators and connectors to find matching companies.

Instructions

Screen Indian stocks by fundamental criteria using 326 financial ratios (valuation, profitability, growth, balance sheet, cash flow, shareholding, with 3Y/5Y/10Y history). For technical screens (RSI, MACD, moving averages), use screen_stocks_technical instead.

QUERY SYNTAX: {Ratio Name} {operator} {value}[%] Operators: >, <, =, >=, <= Connectors: AND, OR (each on its own line) Cross-field comparison is allowed: Current price > DMA 200 Max length 1500 characters. Ratio names must be EXACT.

COMMON RATIO NAMES: Market Capitalization, Current price, Price to Earning, Price to book value, Dividend yield, Return on equity, Return on capital employed, OPM, EPS, Net profit, Sales, Sales growth 3Years, Profit growth 3Years, Debt to equity, Current ratio, Promoter holding, FII holding, Pledged percentage, DMA 50, DMA 200, RSI, Piotroski score, Altman Z Score, Number of equity shares. Call get_screener_ratios (searchable, full 326-ratio catalog) for anything not listed — do not guess a name.

EXAMPLE: "Market Capitalization > 5000 AND\nPrice to Earning < 15 AND\nReturn on capital employed > 22"

Note: "last year" in a ratio name means the most recent annual result. To identify an unknown stock from partial financials, call read_me for the disambiguation procedure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
sortNoSort by ratio name (e.g., 'Market Capitalization')
limitNoResults per page (default 25, max 50 — higher values are clamped)
orderNoSort direction
queryNoREQUIRED. Screener query using ratio names, operators, and AND/OR connectors. Example: "Market Capitalization > 5000 AND Return on capital employed > 22".
latestNoOnly companies with latest quarter results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description goes further by disclosing query syntax constraints, the 1500-character limit, exact ratio-name matching, cross-field comparison allowance, and the meaning of 'last year'. No contradiction with annotations exists.

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?

The description is dense but well-organized with clear sections for query syntax, common ratio names, and an example. Every sentence contributes practical value, with no filler or repetition of the schema.

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?

For a tool with a nontrivial query language and 326 possible ratio names, the description provides everything needed to invoke it correctly: syntax, allowed operators, connectors, examples, exact-name requirement, and fallback routes. The lack of an output schema is not a gap for this selection-use case.

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?

All six parameters already have schema descriptions, so the baseline is 3. The description raises this by providing query grammar, operators, connectors, an example, and a list of common ratio names, substantially enriching the meaning of the query parameter beyond the schema.

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 states a specific verb ('Screen'), resource ('Indian stocks'), and scope ('by fundamental criteria using 326 financial ratios'), and explicitly distinguishes itself from screen_stocks_technical. An agent can immediately tell what this tool does and how it differs from the closest sibling.

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?

It gives explicit routing instructions: use screen_stocks_technical for technical screens, call get_screener_ratios for unknown ratio names, and call read_me for disambiguating unknown stocks. This is clear when-to-use and when-not-to-use guidance with named alternatives.

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

Deploy Server

Other Tools