Skip to main content
Glama

Tapetide - Indian Stock Market MCP

Stock Screener (Fundamental)

screen_stocks
Read-onlyIdempotent

Screen Indian stocks by fundamental criteria using 325 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 (case-insensitive); an invalid query is an error naming the bad token.

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 325-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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "screen_stocks"
  }
}

Input 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. Changed1 schema field changed
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description's job is to add operational detail — and it does: exact-match, case-insensitive ratio names, 1500-character cap, an error on invalid tokens, and the 'last year' convention. It stops short of describing the shape of returned rows, though with pagination and sorting delegated to the schema that gap is modest.

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?

Front-loaded purpose sentence, then a labeled QUERY SYNTAX block, a curated ratio list, an example, and a closing note — each section earns its place and is scannable. The ratio enumeration is long but is the highest-value content for query construction, not padding.

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?

For a query-language tool this is close to complete: grammar, allowed operators, naming rules, escape hatches to helper tools, and an example are all present. The one omission is any hint of what a result row contains, since no output schema exists to carry that.

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 the baseline is 3; the description exceeds that by fully specifying the `query` grammar — operator set, AND/OR connectors on separate lines, cross-field comparison like 'Current price > DMA 200', and a worked example. The remaining five parameters (page, limit, sort, order, latest) are left entirely to 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?

States a specific verb and resource ('Screen Indian stocks by fundamental criteria') with concrete scope (325 financial ratios, history depth) and explicitly names the sibling it is not (screen_stocks_technical) with the condition that separates them. An agent can distinguish the two without opening either schema.

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?

Gives explicit routing: technical screens go to screen_stocks_technical, unknown ratio names go to get_screener_ratios, and partial-financial disambiguation goes to read_me. It also states the failure mode for a malformed query ('an invalid query is an error naming the bad token'), so the agent knows the cost of guessing a name.

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.