read_me returns the full tool guide and usage patterns. Responses about investments must carry a SEBI disclaimer: Tapetide is not a SEBI-registered research analyst or investment adviser, and its data is for research and information only. Independent tool calls can be batched in parallel.
Discoverability
1/6 passed1 of 6 passed17/100
Client listings and public setup information.
mcp.json or server-card.json
Either mcp.json or an MCP Server Card declaring this endpoint passes.
The MCP Server Card declares this server's exact endpoint.
How to fix: For tools that render a UI resource, add openai/toolInvocation with string fields invoking and invoked (present-tense labels shown while the tool runs and after it finishes, e.g. "Searching…" / "Searched").
How to fix: Use a ui:// URI and text/html;profile=mcp-app. For mcp-use v1, use widgetMetadata.metadata.widgetDescription; for v2, use the bound tool's view.description. The current description check reads _meta.ui.widgetDescription or _meta["openai/widgetDescription"] on resource contents or linked tools, not resource.description. Consequently, v2 view.description alone may leave this warning: report the checker compatibility gap instead of adding unsupported v1 fields or claiming the warning is fixed.
How to fix: For ChatGPT submission, set one exact HTTPS origin such as "https://app.example.com" on every view via _meta.ui.domain (or openai/widgetDomain). Paths are not valid and all views in one app must share the origin.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description90/100
Search ~8,000 Indian stocks by name, symbol, BSE code, or ISIN. Also matches common/brand names and post-rename aliases (e.g. 'Zomato'→ETERNAL, 'Infosys'→INFY). Listed companies rank first, then by match (exact symbol/code > prefix > word > contains), larger companies first within each; queries of 4+ characters tolerate typos. Each result's `symbol` is what the per-stock tools take as input.
Describe the returned information so the agent knows whether it will answer the request.
Inputs89/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
query
REQUIRED. The search text — a company name, symbol, BSE code, or ISIN. Example: "reliance" or "TCS".
Clear enough to supply this argument.
sector
Filter by sector (e.g. 'Information Technology')
Clear enough to supply this argument.
industry
Industry, exact match (NSE label, e.g. 'Banks'; some rows still use older labels like 'Private Bank')
Clear enough to supply this argument.
limit
Max results (default 10, max 50)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_stocks",
"title": "Search Indian Stocks",
"description": "Search ~8,000 Indian stocks by name, symbol, BSE code, or ISIN. Also matches common/brand names and post-rename aliases (e.g. 'Zomato'→ETERNAL, 'Infosys'→INFY). Listed companies rank first, then by match (exact symbol/code > prefix > word > contains), larger companies first within each; queries of 4+ characters tolerate typos. Each result's `symbol` is what the per-stock tools take as input.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "number",
"default": 10,
"description": "Max results (default 10, max 50)"
},
"query": {
"type": "string",
"description": "REQUIRED. The search text — a company name, symbol, BSE code, or ISIN. Example: \"reliance\" or \"TCS\"."
},
"sector": {
"type": "string",
"description": "Filter by sector (e.g. 'Information Technology')"
},
"industry": {
"type": "string",
"description": "Industry, exact match (NSE label, e.g. 'Banks'; some rows still use older labels like 'Private Bank')"
}
},
"additionalProperties": false
},
"annotations": {
"title": "Search Indian Stocks",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Get detailed company overview — sector, about, pros/cons, fundamentals (PE, PB, market cap, ROE, ROCE, debt/equity), growth metrics, and current quote. Default response is ~3KB.
Use the 'include' param to add optional sections via parallel API calls:
- "technicals": RSI, SMA, EMA, MACD, Bollinger Bands, ATR, ADX (~20 indicators)
- "ratings": Analyst buy/hold/sell consensus with counts and percentages
- "peers": Comparable-company table — the stock's published peer cohort with price, day change, market cap, P/E, P/B, dividend yield, ROE, ROCE, ROA, OPM, debt/equity, TTM sales and net profit, and promoter holding, plus a per-column median across the cohort. The stock itself is included and flagged `is_self`, so it can be ranked against its own peers on any column. A `null` metric means the figure is not published for that company — never treat it as 0.
- "industry_peers": every traded company in the stock's basic industry, largest first, with 3y revenue/profit growth and 1y return; 50 per call, then peers_cursor = industry_peers.next_cursor.
Also last_split/last_bonus (ratio, ex-date, price_confirmed); split_bonus_unavailable if not read.
Example: include ["technicals", "ratings"] for a full analysis view.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. The stock symbol, e.g. "RELIANCE", "TCS", or "HDFCBANK".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
include
Optional extra sections, a list of: technicals, ratings, peers, industry_peers. Fundamentals, growth and pros/cons are already in the base profile; statements are get_financials.
Clear enough to supply this argument.
peers_cursor
industry_peers next_cursor
Explain the meaning of this value, not just its name.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_company_profile",
"title": "Company Profile",
"description": "Get detailed company overview — sector, about, pros/cons, fundamentals (PE, PB, market cap, ROE, ROCE, debt/equity), growth metrics, and current quote. Default response is ~3KB.\n\nUse the 'include' param to add optional sections via parallel API calls:\n- \"technicals\": RSI, SMA, EMA, MACD, Bollinger Bands, ATR, ADX (~20 indicators)\n- \"ratings\": Analyst buy/hold/sell consensus with counts and percentages\n- \"peers\": Comparable-company table — the stock's published peer cohort with price, day change, market cap, P/E, P/B, dividend yield, ROE, ROCE, ROA, OPM, debt/equity, TTM sales and net profit, and promoter holding, plus a per-column median across the cohort. The stock itself is included and flagged `is_self`, so it can be ranked against its own peers on any column. A `null` metric means the figure is not published for that company — never treat it as 0.\n- \"industry_peers\": every traded company in the stock's basic industry, largest first, with 3y revenue/profit growth and 1y return; 50 per call, then peers_cursor = industry_peers.next_cursor.\n\nAlso last_split/last_bonus (ratio, ex-date, price_confirmed); split_bonus_unavailable if not read.\n\nExample: include [\"technicals\", \"ratings\"] for a full analysis view.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"symbol": {
"type": "string",
"description": "REQUIRED. The stock symbol, e.g. \"RELIANCE\", \"TCS\", or \"HDFCBANK\"."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"include": {
"anyOf": [
{
"type": "array",
"items": {
"type": "string"
}
},
{
"type": "string"
}
],
"description": "Optional extra sections, a list of: technicals, ratings, peers, industry_peers. Fundamentals, growth and pros/cons are already in the base profile; statements are get_financials."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
},
"peers_cursor": {
"type": "string",
"description": "industry_peers next_cursor"
}
},
"additionalProperties": false
},
"annotations": {
"title": "Company Profile",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description89/100
Get stock events — news, corporate actions, or company filings.
Types:
- "news": Sentiment-tagged news (positive/negative/neutral), category, source URL
- "corporate_actions": Dividends, splits, bonuses, AGMs, rights issues with ex-date and LTP
- "filings": Results, presentations, concall transcripts/audio, annual reports, credit ratings, announcements. Rows carry doc_type and the exact filing date, latest quarter included.
Paging: max 50 per call; while meta.has_more, pass offset=meta.next_offset. from/to (filings only) bound the date; meta.total is for the filtered set.
The description explains the capability, when to use it, and what to expect.
Inputs77/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. The stock symbol, e.g. "RELIANCE" or "TCS".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
type
Event type to fetch. Defaults to "news" when omitted.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Max results (default 20, max 50)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
offset
Rows to skip (news/filings); pass meta.next_offset.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Get ownership data for a stock — yearly dividend totals and mutual fund holdings. `dividends` is one row per year: {Year, Div (dividend per share in ₹ for that year), yield (%), exch}. There is NO ex-date and NO interim/final split here; for dated individual dividends use get_stock_events with type "corporate_actions". `dividends` is an empty string or null when none is on file. `mf_holdings` is a list of positional arrays, one per scheme: [scheme_id, scheme_name, amc_id, scheme_isin, shares_held, pct_of_scheme_aum, share_change_mom, pct_of_aum_change_mom (percentage points), an unlabelled change figure (do not interpret), months, slug]. shares_held, pct_of_scheme_aum and months are '|'-joined monthly series, newest first, aligned by position (e.g. months "2026-09|2026-08|…"). Empty string or null when no holdings are on file.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. The stock symbol, e.g. "RELIANCE" or "TCS".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
identifier
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_stock_ownership",
"title": "Stock Ownership",
"description": "Get ownership data for a stock — yearly dividend totals and mutual fund holdings. `dividends` is one row per year: {Year, Div (dividend per share in ₹ for that year), yield (%), exch}. There is NO ex-date and NO interim/final split here; for dated individual dividends use get_stock_events with type \"corporate_actions\". `dividends` is an empty string or null when none is on file. `mf_holdings` is a list of positional arrays, one per scheme: [scheme_id, scheme_name, amc_id, scheme_isin, shares_held, pct_of_scheme_aum, share_change_mom, pct_of_aum_change_mom (percentage points), an unlabelled change figure (do not interpret), months, slug]. shares_held, pct_of_scheme_aum and months are '|'-joined monthly series, newest first, aligned by position (e.g. months \"2026-09|2026-08|…\"). Empty string or null when no holdings are on file.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"symbol": {
"type": "string",
"description": "REQUIRED. The stock symbol, e.g. \"RELIANCE\" or \"TCS\"."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Stock Ownership",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Latest stock quote: LTP, change, change %, volume, market cap, PE, 52-week high/low. price_basis is live (traded today or in the last session), last_trade (an older session's price) or null (unknown). last_trade_date is the session the price traded in. NSE prices can lag the exchange by up to ~15 minutes. For multiple stocks, use get_batch_quotes instead.
The description explains the capability, when to use it, and what to expect.
Inputs44/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. The stock symbol, e.g. "RELIANCE" or "TCS".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Explain the meaning of this value, not just its name.
identifier
Alias for `symbol`.
Explain the meaning of this value, not just its name.
symbols
Alias for `symbol`: exactly one.
Resolve the mismatch between this description and its schema constraints.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description74/100
Quotes for up to 20 stocks in one call, each with price_basis and last_trade_date as in get_stock_quote. NSE prices can lag the exchange by up to ~15 minutes.
The description explains the capability, when to use it, and what to expect.
Inputs68/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbols
REQUIRED. Array of up to 20 stock symbols, e.g. ["RELIANCE","TCS","HDFCBANK"]. Over 20, split across calls.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_batch_quotes",
"title": "Batch Stock Quotes",
"description": "Quotes for up to 20 stocks in one call, each with price_basis and last_trade_date as in get_stock_quote. NSE prices can lag the exchange by up to ~15 minutes.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"symbols": {
"anyOf": [
{
"type": "array",
"items": {
"anyOf": [
{
"type": "string"
}
]
}
},
{
"type": "string"
}
],
"description": "REQUIRED. Array of up to 20 stock symbols, e.g. [\"RELIANCE\",\"TCS\",\"HDFCBANK\"]. Over 20, split across calls."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Batch Stock Quotes",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Get OHLCV price history as row-per-day format — date, open, high, low, close, raw_close, volume. Supports configurable lookback days and daily/weekly aggregation. Default 365 days (max 2000). Use this for price analysis, trend detection, and technical calculations. IMPORTANT: check `meta.window` before treating the series as complete. `days` is CAPPED at 2000 (`meta.window.truncated`), and a window over the ~25k-char result limit keeps the newest bars (`meta.truncated`). Either way `meta.window.has_more: true` means older bars exist: pass `meta.window.next_cursor` as `end_date`, and page until `meta.window.has_more` is false.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. The stock symbol, e.g. "RELIANCE" or "TCS".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
days
Number of days to look back (default 365, max 2000 — larger values are capped, see meta.window)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
interval
Bar size: "daily" (default) or "weekly" — the AGGREGATION of each row, NOT the length of the window. Use `days` for the window (e.g. days:5 for the last 5 sessions). Only end-of-day bars exist: intraday values like "1m"/"5m"/"15m"/"1h" and "monthly" are NOT supported and return an explanatory error.
Clear enough to supply this argument.
end_date
Optional YYYY-MM-DD upper bound (inclusive) for the window — the cursor for paging further back through history. Pass the `meta.window.next_cursor` from a truncated response to fetch the preceding page. Omit for the most recent window.
Clear enough to supply this argument.
ticker
Alias for `symbol`.
Clear enough to supply this argument.
identifier
Alias for `symbol`.
Explain the meaning of this value, not just its name.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_price_history",
"title": "Price History (OHLCV)",
"description": "Get OHLCV price history as row-per-day format — date, open, high, low, close, raw_close, volume. Supports configurable lookback days and daily/weekly aggregation. Default 365 days (max 2000). Use this for price analysis, trend detection, and technical calculations. IMPORTANT: check `meta.window` before treating the series as complete. `days` is CAPPED at 2000 (`meta.window.truncated`), and a window over the ~25k-char result limit keeps the newest bars (`meta.truncated`). Either way `meta.window.has_more: true` means older bars exist: pass `meta.window.next_cursor` as `end_date`, and page until `meta.window.has_more` is false.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"days": {
"type": "number",
"default": 365,
"description": "Number of days to look back (default 365, max 2000 — larger values are capped, see meta.window)"
},
"symbol": {
"type": "string",
"description": "REQUIRED. The stock symbol, e.g. \"RELIANCE\" or \"TCS\"."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"end_date": {
"type": "string",
"description": "Optional YYYY-MM-DD upper bound (inclusive) for the window — the cursor for paging further back through history. Pass the `meta.window.next_cursor` from a truncated response to fetch the preceding page. Omit for the most recent window."
},
"interval": {
"type": "string",
"default": "daily",
"description": "Bar size: \"daily\" (default) or \"weekly\" — the AGGREGATION of each row, NOT the length of the window. Use `days` for the window (e.g. days:5 for the last 5 sessions). Only end-of-day bars exist: intraday values like \"1m\"/\"5m\"/\"15m\"/\"1h\" and \"monthly\" are NOT supported and return an explanatory error."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Price History (OHLCV)",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Get financial statements for one company. Sections: `quarterly` (quarterly P&L), `profit_loss` (annual P&L), `balance_sheet`, `cash_flow`, `ratios` (all annual). Default: the latest periods with growth rates (`quarterly` ~13 quarters); omit `section` for all sections trimmed to 5 periods each (`periods` widens, e.g. {"symbol":"TCS","section":"quarterly","periods":12}). Each section carries `periods` (oldest first), `data` {row: {period: value}}, `pct_changes`, `row_order` and `availability` with each period's point-in-time `available_from`. LONG HISTORY: pass `section` with `from`, `to`, `as_of` or `basis` for a period table (broad from FY2015, sparse before), up to 60 periods per call, newest first; when `meta.next_to` is set, call again with `to` = that date for older periods. That table's `eps_basis`: as_reported, restated or null. `as_of` returns only what was public then (backtests); values may include later restatements. One symbol per call; to compare companies use get_batch_financials. ETFs, index funds and bonds have no statements.
The description explains the capability, when to use it, and what to expect.
Inputs79/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. The stock symbol, e.g. "RELIANCE" or "TCS".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
section
One of: quarterly, profit_loss, balance_sheet, cash_flow, ratios. `quarterly` is the quarterly P&L; the other four are annual. Omit for all sections.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
periods
Latest N periods per section (max 40). Default: all periods when a section is named, 5 per section when it is not.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
quarters
Alias for `periods`.
Clear enough to supply this argument.
from
History: earliest period end, YYYY-MM-DD.
Clear enough to supply this argument.
to
History: latest period end, YYYY-MM-DD (`meta.next_to` for the next page).
Clear enough to supply this argument.
as_of
History: only figures public by this date, YYYY-MM-DD.
Clear enough to supply this argument.
basis
History: preferred (default), consolidated or standalone.
Explain the meaning of this value, not just its name.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_financials",
"title": "Financial Statements",
"description": "Get financial statements for one company. Sections: `quarterly` (quarterly P&L), `profit_loss` (annual P&L), `balance_sheet`, `cash_flow`, `ratios` (all annual). Default: the latest periods with growth rates (`quarterly` ~13 quarters); omit `section` for all sections trimmed to 5 periods each (`periods` widens, e.g. {\"symbol\":\"TCS\",\"section\":\"quarterly\",\"periods\":12}). Each section carries `periods` (oldest first), `data` {row: {period: value}}, `pct_changes`, `row_order` and `availability` with each period's point-in-time `available_from`. LONG HISTORY: pass `section` with `from`, `to`, `as_of` or `basis` for a period table (broad from FY2015, sparse before), up to 60 periods per call, newest first; when `meta.next_to` is set, call again with `to` = that date for older periods. That table's `eps_basis`: as_reported, restated or null. `as_of` returns only what was public then (backtests); values may include later restatements. One symbol per call; to compare companies use get_batch_financials. ETFs, index funds and bonds have no statements.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"to": {
"type": "string",
"description": "History: latest period end, YYYY-MM-DD (`meta.next_to` for the next page)."
},
"from": {
"type": "string",
"description": "History: earliest period end, YYYY-MM-DD."
},
"as_of": {
"type": "string",
"description": "History: only figures public by this date, YYYY-MM-DD."
},
"basis": {
"type": "string",
"description": "History: preferred (default), consolidated or standalone."
},
"symbol": {
"type": "string",
"description": "REQUIRED. The stock symbol, e.g. \"RELIANCE\" or \"TCS\"."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"periods": {
"type": [
"number",
"string"
],
"description": "Latest N periods per section (max 40). Default: all periods when a section is named, 5 per section when it is not."
},
"section": {
"type": "string",
"description": "One of: quarterly, profit_loss, balance_sheet, cash_flow, ratios. `quarterly` is the quarterly P&L; the other four are annual. Omit for all sections."
},
"quarters": {
"type": [
"number",
"string"
],
"description": "Alias for `periods`."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Financial Statements",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
Get shareholding pattern — promoter, FII, DII, public holdings over time. Track institutional buying/selling trends quarter over quarter. Useful for understanding ownership changes. CAUTION: a move of more than 5 points in any bucket in a single quarter may be a filing reclassification rather than trading. When you see one, report the public/other buckets for the same quarters alongside it and do not describe the move as accumulation or exit without a second source.
The description explains the capability, when to use it, and what to expect.
Inputs63/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. The stock symbol, e.g. "RELIANCE" or "TCS".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
type
Period type. Omit for all.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Explain the meaning of this value, not just its name.
identifier
Alias for `symbol`.
Explain the meaning of this value, not just its name.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_shareholding",
"title": "Shareholding Pattern",
"description": "Get shareholding pattern — promoter, FII, DII, public holdings over time. Track institutional buying/selling trends quarter over quarter. Useful for understanding ownership changes. CAUTION: a move of more than 5 points in any bucket in a single quarter may be a filing reclassification rather than trading. When you see one, report the public/other buckets for the same quarters alongside it and do not describe the move as accumulation or exit without a second source.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"type": {
"enum": [
"quarterly",
"annual"
],
"type": "string",
"description": "Period type. Omit for all."
},
"symbol": {
"type": "string",
"description": "REQUIRED. The stock symbol, e.g. \"RELIANCE\" or \"TCS\"."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Shareholding Pattern",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
Get analyst forecasts — EPS, revenue, EBITDA, net income, ROA, ROE, and price estimates. Both quarterly and annual periods with actuals vs estimates comparison, and each estimate's analyst range in `bands` (low/high). EPS actuals are restated for splits and bonuses; `meta.eps_adjustments` lists what was rescaled. Useful for understanding market expectations and earnings surprises.
The description explains the capability, when to use it, and what to expect.
Inputs66/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. The stock symbol, e.g. "RELIANCE" or "TCS".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Explain the meaning of this value, not just its name.
identifier
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
One financial statement section for up to 10 companies in one call, for comparing them: the same numbers and available_from dates as get_financials, latest `periods` per company. Results are in input order, one per symbol; a symbol that fails gets found:false and the reason. Charged as one call per company found.
The description explains the capability, when to use it, and what to expect.
Inputs66/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbols
REQUIRED. Up to 10 stock symbols, e.g. ["TCS","INFY"].
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
section
quarterly (default), profit_loss, balance_sheet, cash_flow or ratios.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
periods
Latest N periods per company (default 6, max 12).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_batch_financials",
"title": "Batch Financial Statements",
"description": "One financial statement section for up to 10 companies in one call, for comparing them: the same numbers and available_from dates as get_financials, latest `periods` per company. Results are in input order, one per symbol; a symbol that fails gets found:false and the reason. Charged as one call per company found.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"periods": {
"type": [
"number",
"string"
],
"description": "Latest N periods per company (default 6, max 12)."
},
"section": {
"type": "string",
"description": "quarterly (default), profit_loss, balance_sheet, cash_flow or ratios."
},
"symbols": {
"anyOf": [
{
"type": "array",
"items": {
"anyOf": [
{
"type": "string"
}
]
}
},
{
"type": "string"
}
],
"description": "REQUIRED. Up to 10 stock symbols, e.g. [\"TCS\",\"INFY\"]."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Batch Financial Statements",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Today's snapshot: FII/DII net flows (crores), Nifty 50 PE/PB/DY, India VIX, global indices (S&P 500, Dow, Nasdaq...), gold/silver/crude closes, USD/INR. Quick daily overview. For the technical signal scanner (52-week highs/lows, RSI extremes, MACD, volume spikes) use get_market_data with dataset: "signals"; for top gainers/losers/most-active use get_trending_stocks.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
Get detailed FII/DII institutional flow data:
- Daily cash market flows for last 30 trading days (buy/sell/net in crores)
- F&O participant positioning (FII/DII/Pro/Client long/short OI)
- Weekly, monthly, yearly aggregates
- Buy/sell streaks and 5d/30d/1yr cumulative net flows
- Optional: cumulative flow chart data with interval param
Essential for understanding institutional money flow in Indian markets.
The description explains the capability, when to use it, and what to expect.
Inputs68/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
chart_interval
Include cumulative flow chart data for this interval
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Shorten the title to an action and subject; move usage details into the description.
Description70/100
Alias for get_fii_dii_detail. Get detailed FII/DII institutional flow data — daily cash market flows, F&O positioning, weekly/monthly/yearly aggregates, buy/sell streaks.
The description explains the capability, when to use it, and what to expect.
Inputs52/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
chart_interval
Include cumulative flow chart data for this interval
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Get FPI (Foreign Portfolio Investor) sector-wise investment data. Returns AUM share per sector, fortnight change, 1-year cumulative flow, and sparkline data. Sorted three ways: by AUM, by fortnight change, and by 1Y flow. Useful for understanding which sectors foreign investors are buying/selling.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Get latest market-wide news across all categories. Returns sentiment-tagged articles (positive/negative/neutral) with category, source URL, and related stock symbols.
Categories include: companies, global, markets, ipo, government-policy-and-regulation, debt-markets, equity-markets, investment-ideas, technology, real-estate, infrastructure.
Use this for broad market news. For stock-specific news, use get_stock_events with type "news" instead.
The description explains the capability, when to use it, and what to expect.
Inputs71/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Max results (default 20, max 50)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
category
Filter by category (e.g. 'global', 'markets', 'ipo', 'companies')
Clear enough to supply this argument.
sentiment
Filter by sentiment
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Get one of today's market-wide data feeds. Pass `dataset` to choose:
- deals — bulk & block deals for the last 7 days (symbol, name, client, buy/sell, qty, price, value), newest and largest first.
- fno_ban — F&O ban list: stocks at or above 80% of MWPL, with mwpl_pct and status (in_ban from the exchange's published ban list, else near_ban).
- deliveries — latest session's highest delivery-% stocks (>=50%, traded value >= Rs 1 Cr), indicating genuine buying over speculation.
- ipo — current and upcoming IPOs: dates, price band, issue size, and subscription by category.
- mtf — Margin Trading Facility: most-funded stocks with funded qty/value in Rs crore and change vs the previous session (market-wide book not available).
- slbm — Stock Lending & Borrowing: lent stocks with lending yield and traded qty. High yield = strong short-selling demand.
- signals — technical signals from the latest session: 52-week highs/lows, RSI extremes, MACD, volume spikes, 200-day trend.
For index PE/PB valuation history use market_valuations; for an index's constituent heatmap use market_heatmap; for a single stock's own deal history use get_stock_deals.
The description explains the capability, when to use it, and what to expect.
Inputs55/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
dataset
REQUIRED. Which feed to fetch: deals, fno_ban, deliveries, ipo, mtf, slbm, signals.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
data_type
Alias for `dataset`.
Explain the meaning of this value, not just its name.
type
Alias for `dataset`.
Explain the meaning of this value, not just its name.
category
Alias for `dataset`.
Explain the meaning of this value, not just its name.
feed
Alias for `dataset`.
Explain the meaning of this value, not just its name.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_market_data",
"title": "Market Data Feeds",
"description": "Get one of today's market-wide data feeds. Pass `dataset` to choose:\n- deals — bulk & block deals for the last 7 days (symbol, name, client, buy/sell, qty, price, value), newest and largest first.\n- fno_ban — F&O ban list: stocks at or above 80% of MWPL, with mwpl_pct and status (in_ban from the exchange's published ban list, else near_ban).\n- deliveries — latest session's highest delivery-% stocks (>=50%, traded value >= Rs 1 Cr), indicating genuine buying over speculation.\n- ipo — current and upcoming IPOs: dates, price band, issue size, and subscription by category.\n- mtf — Margin Trading Facility: most-funded stocks with funded qty/value in Rs crore and change vs the previous session (market-wide book not available).\n- slbm — Stock Lending & Borrowing: lent stocks with lending yield and traded qty. High yield = strong short-selling demand.\n- signals — technical signals from the latest session: 52-week highs/lows, RSI extremes, MACD, volume spikes, 200-day trend.\nFor index PE/PB valuation history use market_valuations; for an index's constituent heatmap use market_heatmap; for a single stock's own deal history use get_stock_deals.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"feed": {
"type": "string",
"description": "Alias for `dataset`."
},
"type": {
"type": "string",
"description": "Alias for `dataset`."
},
"dataset": {
"enum": [
"deals",
"fno_ban",
"deliveries",
"ipo",
"mtf",
"slbm",
"signals"
],
"type": "string",
"description": "REQUIRED. Which feed to fetch: deals, fno_ban, deliveries, ipo, mtf, slbm, signals."
},
"category": {
"type": "string",
"description": "Alias for `dataset`."
},
"data_type": {
"type": "string",
"description": "Alias for `dataset`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Market Data Feeds",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description79/100
Get index valuation metrics (PE, PB, Dividend Yield) over time. Default: Nifty 50, weekly data, 5 years. Useful for assessing whether the market is overvalued or undervalued relative to historical averages.
index_code accepts EITHER a slug (recommended, like market_heatmap) or a raw numeric code:
nifty-50 (13), nifty-500 (19), nifty-bank (25), nifty-midcap-50 (51), nifty-it (27), nifty-next-50 (53).
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
index_code
Index as a slug ("nifty-50", "nifty-bank", "nifty-it", "nifty-500", "nifty-midcap-50", "nifty-next-50") or its numeric code. Default "nifty-50".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
years
Years of history (default 5, max 20)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description85/100
Get a stock heatmap for an index — all constituent stocks with market cap, PE, PB, price changes (1d/1w/1m/3m/6m/1y/5y), volume, and sector.
Available indices: see the index parameter (Nifty broad, size and sector indices plus Sensex).
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description83/100
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.
The description explains the capability, when to use it, and what to expect.
Inputs64/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
query
REQUIRED. Screener query using ratio names, operators, and AND/OR connectors. Example: "Market Capitalization > 5000 AND Return on capital employed > 22".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
sort
Sort by ratio name (e.g., 'Market Capitalization')
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
order
Sort direction
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Results per page (default 25, max 50 — higher values are clamped)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
page
Page number
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
latest
Only companies with latest quarter results
Explain what happens when this optional value is omitted.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "screen_stocks",
"title": "Stock Screener (Fundamental)",
"description": "Screen Indian stocks by fundamental criteria using 325 financial ratios (valuation, profitability, growth, balance sheet, cash flow, shareholding, with 3Y/5Y/10Y history).\nFor technical screens (RSI, MACD, moving averages), use screen_stocks_technical instead.\n\nQUERY SYNTAX: {Ratio Name} {operator} {value}[%]\n Operators: >, <, =, >=, <= Connectors: AND, OR (each on its own line)\n Cross-field comparison is allowed: Current price > DMA 200\n Max length 1500 characters. Ratio names must be EXACT (case-insensitive); an invalid query is an error naming the bad token.\n\nCOMMON 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.\nCall get_screener_ratios (searchable, full 325-ratio catalog) for anything not listed — do not guess a name.\n\nEXAMPLE: \"Market Capitalization > 5000 AND\\nPrice to Earning < 15 AND\\nReturn on capital employed > 22\"\n\nNote: \"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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"page": {
"type": "number",
"default": 1,
"minimum": 1,
"description": "Page number"
},
"sort": {
"type": "string",
"description": "Sort by ratio name (e.g., 'Market Capitalization')"
},
"limit": {
"type": "number",
"default": 25,
"minimum": 1,
"description": "Results per page (default 25, max 50 — higher values are clamped)"
},
"order": {
"enum": [
"asc",
"desc"
],
"type": "string",
"description": "Sort direction"
},
"query": {
"type": "string",
"maxLength": 1500,
"description": "REQUIRED. Screener query using ratio names, operators, and AND/OR connectors. Example: \"Market Capitalization > 5000 AND Return on capital employed > 22\"."
},
"latest": {
"type": "boolean",
"description": "Only companies with latest quarter results"
}
},
"additionalProperties": true
},
"annotations": {
"title": "Stock Screener (Fundamental)",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Search or list available financial ratios for the screen_stocks tool. Pass a keyword to search (e.g., 'cash flow', 'debt', 'promoter') or omit for the full catalog of 325 ratios. Returns the exact ratio names that screen_stocks queries accept.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Input documentation gives an agent enough context to populate the arguments.
q
Search keyword (e.g., 'cash', 'debt', 'growth'). Omit for full catalog.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_screener_ratios",
"title": "Screener Ratio Lookup",
"description": "Search or list available financial ratios for the screen_stocks tool. Pass a keyword to search (e.g., 'cash flow', 'debt', 'promoter') or omit for the full catalog of 325 ratios. Returns the exact ratio names that screen_stocks queries accept.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"q": {
"type": "string",
"description": "Search keyword (e.g., 'cash', 'debt', 'growth'). Omit for full catalog."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Screener Ratio Lookup",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description88/100
Get derivatives analytics for a stock — implied volatility (ATM IV, IV rank, IV percentile), realized volatility, put-call ratio (OI and volume), max pain strike, 25-delta skew, and call/put open interest, broken down per expiry. Use for options strategy, volatility analysis, and gauging derivatives-market positioning.
The description explains the capability, when to use it, and what to expect.
Inputs58/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. Stock symbol, e.g. "RELIANCE" or "TCS".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Explain the meaning of this value, not just its name.
identifier
Alias for `symbol`.
Explain the meaning of this value, not just its name.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Get large-trade history for a stock — bulk deals, block deals, insider (designated-person) trades, and SAST (substantial acquisition) disclosures, with the counterparty name, buy/sell side, quantity, price, and value, newest first. Insider/SAST rows are filings (`record`: filing, with disclosure date, category, holdings) or older summary rows for months without filings (`record`: summary; see meta.coverage_note). Answers 'who has been buying or selling X?'. Optionally filter by deal type. `price` is as traded; `price_adjusted` is the same price on the split/bonus-adjusted basis of the daily closes, so compare a pre-split/bonus deal with the close using `price_adjusted`. While meta.has_more, pass meta.next_cursor as `cursor`.
The description explains the capability, when to use it, and what to expect.
Inputs85/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. Stock symbol, e.g. "RELIANCE" or "TCS".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
type
Filter to a single deal type. Omit for all types.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Max deals (default 25, max 100)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
cursor
meta.next_cursor of the previous page (same symbol and type).
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_stock_deals",
"title": "Bulk, Block & Insider Deals",
"description": "Get large-trade history for a stock — bulk deals, block deals, insider (designated-person) trades, and SAST (substantial acquisition) disclosures, with the counterparty name, buy/sell side, quantity, price, and value, newest first. Insider/SAST rows are filings (`record`: filing, with disclosure date, category, holdings) or older summary rows for months without filings (`record`: summary; see meta.coverage_note). Answers 'who has been buying or selling X?'. Optionally filter by deal type. `price` is as traded; `price_adjusted` is the same price on the split/bonus-adjusted basis of the daily closes, so compare a pre-split/bonus deal with the close using `price_adjusted`. While meta.has_more, pass meta.next_cursor as `cursor`.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"type": {
"enum": [
"bulk",
"block",
"insider",
"sast"
],
"type": "string",
"description": "Filter to a single deal type. Omit for all types."
},
"limit": {
"type": "number",
"default": 25,
"description": "Max deals (default 25, max 100)"
},
"cursor": {
"type": "string",
"description": "meta.next_cursor of the previous page (same symbol and type)."
},
"symbol": {
"type": "string",
"description": "REQUIRED. Stock symbol, e.g. \"RELIANCE\" or \"TCS\"."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Bulk, Block & Insider Deals",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description82/100
Promoter share-pledge history for a stock: % of promoter holding pledged by quarter (from Jun 2017, each with available_from), plus pledge creation/release events from 2015, paged. High or rising pledges are a governance red flag. pct_total_shares_pledged is ALL pledged shares (any holder), not promoter-only; see `field_notes`.
The description explains the capability, when to use it, and what to expect.
Inputs74/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. Stock symbol, e.g. "RELIANCE" or "TCS".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
identifier
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
quarters
Latest N quarters (default 12, max 60)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Events per page (default 10, max 100)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
offset
Events to skip; pass events_page.next_offset
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description87/100
Get credit-rating actions for a company — agency, rating, action (upgrade/downgrade/reaffirm), and outlook over time. A rating change is a forward-looking signal on credit/solvency risk. Use for risk assessment and debt-investor research.
The description explains the capability, when to use it, and what to expect.
Inputs67/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. Stock symbol, e.g. "RELIANCE" or "TCS".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Explain the meaning of this value, not just its name.
identifier
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description90/100
Get AI-generated investor digests of a company's recent earnings (concall) transcripts and investor presentations — a structured summary plus key highlights, risks, management guidance, and headline metrics, grounded in the company's own filings. Use for qualitative fundamental research beyond the numbers.
The description explains the capability, when to use it, and what to expect.
Inputs73/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. Stock symbol, e.g. "RELIANCE" or "TCS".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Number of recent summaries (default 2, max 5)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Clear enough to supply this argument.
identifier
Alias for `symbol`.
Explain the meaning of this value, not just its name.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Get the India VIX — the market's expected near-term volatility (the 'fear gauge'). Returns the latest value, daily change, and recent history. Rising VIX = rising fear/uncertainty; falling VIX = calm. Use for market-timing and risk context.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
Companies that filed quarterly results in a time window, newest first. One row per company and quarter: `filed_at` (latest results filing, IST), `declared_at` (first original filing held, or null), `revision`, and revenue and net profit in INR crore as filed (`basis` consolidated when filed, else standalone; revenue is interest earned for banks, can be null). Answers "who reported today"; with `symbols` (up to 500) it checks a whole list in one call, so call get_financials only for the stocks that changed. If `meta.has_more`, repeat with `since` = `meta.since` and `until` = `meta.next_until`. NSE and BSE filings from August 2026 on.
The description explains the capability, when to use it, and what to expect.
Inputs87/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
since
Window start, inclusive: YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS, IST. Default: start of yesterday.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
until
Window end, exclusive, same formats. Default: now.
Clear enough to supply this argument.
symbols
Only these stocks: NSE symbols or BSE scrip codes, e.g. ["VOLTAS","UPL"]. Omit for every company.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_results_declared",
"title": "Results Declared",
"description": "Companies that filed quarterly results in a time window, newest first. One row per company and quarter: `filed_at` (latest results filing, IST), `declared_at` (first original filing held, or null), `revision`, and revenue and net profit in INR crore as filed (`basis` consolidated when filed, else standalone; revenue is interest earned for banks, can be null). Answers \"who reported today\"; with `symbols` (up to 500) it checks a whole list in one call, so call get_financials only for the stocks that changed. If `meta.has_more`, repeat with `since` = `meta.since` and `until` = `meta.next_until`. NSE and BSE filings from August 2026 on.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": [
"number",
"string"
],
"description": "Rows per call (default 50, max 50)."
},
"since": {
"type": "string",
"description": "Window start, inclusive: YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS, IST. Default: start of yesterday."
},
"until": {
"type": "string",
"description": "Window end, exclusive, same formats. Default: now."
},
"symbols": {
"anyOf": [
{
"type": "array",
"items": {
"anyOf": [
{
"type": "string"
}
]
}
},
{
"type": "string"
}
],
"description": "Only these stocks: NSE symbols or BSE scrip codes, e.g. [\"VOLTAS\",\"UPL\"]. Omit for every company."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Results Declared",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
Bank and NBFC metrics for one stock with quarterly history and an `available_from` (filing) date per value: gross/net NPA (INR crore and %), CET1, AT1 and Tier 1 %, provisions, operating expenses, interest, deposits, advances / loans, borrowings, and a computed NIM (`computed: true`). Banks from 2022; NBFCs from 2021 (no NPA or capital ratios in their filings). `quality` marks doubtful values, e.g. reported_value_is_total_crar when a bank filed total CRAR as CET1. CRAR and CASA are not available. Read `meta.field_notes`. Pass `as_of` for point-in-time values. If `meta.has_more`, call again with `cursor`.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. Stock symbol, e.g. "HDFCBANK".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
metrics
Metric names (array or comma-separated). Default: all. One of: gross_npa, net_npa, gross_npa_pct, net_npa_pct, cet1_pct, additional_tier1_pct, tier1_pct, provisions, operating_expenses, operating_profit_before_provisions, credit_cost, interest_earned, interest_expended, finance_costs, nim_pct, deposits, advances, loans, investments, borrowings, debt_securities.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
basis
Statement basis. Default: both. Banks file asset quality and capital on standalone.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
from
Earliest period end, YYYY-MM-DD.
Clear enough to supply this argument.
to
Latest period end, YYYY-MM-DD.
Clear enough to supply this argument.
as_of
Only values filed on or before this date, YYYY-MM-DD. Default: today.
Clear enough to supply this argument.
order
By period end. Default: desc (latest first).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
cursor
`meta.next_cursor` from the previous call; repeat every other argument unchanged.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description88/100
Index of a company's filings parsed to text (concall transcripts, annual reports, presentations, IPO documents): doc_id, type, period, date, num_pages, flags, and per-document links (raw PDF, full Markdown, summary Markdown). No prose. The doc_id is the input get_document_summary and read_document take; the links let the user open or download the document. Newest first.
The description explains the capability, when to use it, and what to expect.
Inputs79/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. Stock symbol, e.g. "RELIANCE".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
doc_types
Restrict to these types (default all).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
since
Only filings on/after YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Max 50.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Investor digest of ONE parsed filing: summary, highlights, risks, guidance, key metrics, plus links to the PDF and full Markdown. Pass doc_id from list_company_documents, or doc_type for the newest of that type. For the text itself use read_document or download links.markdown_url.
The description explains the capability, when to use it, and what to expect.
Inputs80/100
Resolve the mismatch between this description and its schema constraints.
symbol
Stock symbol, e.g. "RELIANCE". Required unless doc_id is given (a doc_id names its company).
Resolve the mismatch between this description and its schema constraints.
doc_id
From list_company_documents. Sufficient on its own.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_document_summary",
"title": "Document Summary",
"description": "Investor digest of ONE parsed filing: summary, highlights, risks, guidance, key metrics, plus links to the PDF and full Markdown. Pass doc_id from list_company_documents, or doc_type for the newest of that type. For the text itself use read_document or download links.markdown_url.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"doc_id": {
"type": "integer",
"description": "From list_company_documents. Sufficient on its own."
},
"symbol": {
"type": "string",
"description": "Stock symbol, e.g. \"RELIANCE\". Required unless doc_id is given (a doc_id names its company)."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"doc_type": {
"enum": [
"concall",
"annual_report",
"presentation",
"drhp",
"rhp"
],
"type": "string",
"description": "Newest of this type when doc_id is omitted."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Document Summary",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Markdown text of a parsed filing by doc_id and page range, with <!-- page N --> markers to cite. Max 12 pages / 24000 chars per call (max_chars up to 60000); the result states pages_returned, next_pages, and links to the full Markdown and PDF. Annual reports run 100-400 pages: read the sections you need, or download links.markdown_url to search the whole file.
The description explains the capability, when to use it, and what to expect.
Inputs54/100
5 of 6 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
symbol
Stock symbol, e.g. "RELIANCE". Optional: doc_id alone identifies the company.
Clear enough to supply this argument.
doc_id
From list_company_documents.
Explain the meaning of this value, not just its name.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Get the Tapetide Score for ONE stock: a deterministic, non-LLM 0-100 composite from the latest complete scoring run, with the six pillar sub-scores and their weights, the percentile within that run (base: `percentile_universe`), confidence, coverage, and `governance` caps and red flags. There is no band field: band = Strong 66+, Good 55-65, Average 45-54, Weak 37-44, Poor <37 (as in screen_tapetide_scores). USE THIS for 'what is Tapetide's score for X', 'why is X rated Y', or as the rating input to a write-up. HOW TO READ IT: (1) the band matters more than the number: the distribution is narrow and a 1-3 point gap is noise; (2) a `null` pillar means the data is unavailable, NOT a zero: never average over it or call the company weak on it; (3) `status: "insufficient_data"` means no publishable score: say so, never substitute a number; (4) `governance.caps_applied` / `red_flags` mean an overlay limited the score, worth saying; (5) there is deliberately NO category label: describe the pillar numbers in your own words. Decision-support only. The Tapetide Score is data analysis, not investment advice. Tapetide is not a SEBI-registered research analyst or investment adviser. Bands are intentionally coarse; small point differences may not be meaningful.
The description explains the capability, when to use it, and what to expect.
Inputs56/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. The stock symbol, e.g. "RELIANCE" or "NATIONALUM".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
identifier
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbols
Alias for `symbol`: exactly one.
Resolve the mismatch between this description and its schema constraints.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_tapetide_score",
"title": "Tapetide Score (one stock)",
"description": "Get the Tapetide Score for ONE stock: a deterministic, non-LLM 0-100 composite from the latest complete scoring run, with the six pillar sub-scores and their weights, the percentile within that run (base: `percentile_universe`), confidence, coverage, and `governance` caps and red flags. There is no band field: band = Strong 66+, Good 55-65, Average 45-54, Weak 37-44, Poor <37 (as in screen_tapetide_scores). USE THIS for 'what is Tapetide's score for X', 'why is X rated Y', or as the rating input to a write-up. HOW TO READ IT: (1) the band matters more than the number: the distribution is narrow and a 1-3 point gap is noise; (2) a `null` pillar means the data is unavailable, NOT a zero: never average over it or call the company weak on it; (3) `status: \"insufficient_data\"` means no publishable score: say so, never substitute a number; (4) `governance.caps_applied` / `red_flags` mean an overlay limited the score, worth saying; (5) there is deliberately NO category label: describe the pillar numbers in your own words. Decision-support only. The Tapetide Score is data analysis, not investment advice. Tapetide is not a SEBI-registered research analyst or investment adviser. Bands are intentionally coarse; small point differences may not be meaningful.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"symbol": {
"type": "string",
"description": "REQUIRED. The stock symbol, e.g. \"RELIANCE\" or \"NATIONALUM\"."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"symbols": {
"type": "array",
"items": {
"type": "string"
},
"description": "Alias for `symbol`: exactly one."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Tapetide Score (one stock)",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
List and rank stocks by the Tapetide Score, filtered by size bucket, band, score window, sector, minimum data-confidence and symbol/name search. Rows come back in the server's final order with score, band, pillars, sector, size, market cap and a next-page cursor. USE THIS for 'which large caps score highest', 'show me Strong-band pharma stocks', or any rank/filter-by-Tapetide-Score question — same data and ordering as the tapetide.com ranking page. IMPORTANT, or you will describe the results wrongly: (1) present rows by BAND, never as an ordinal '#1, #2, #3' leaderboard — nothing has ever scored above 77 and neighbouring scores are not meaningfully different; (2) the DEFAULT view is large+mid cap at confidence >= 75, a filtered slice and not the whole market, so state the active filters (`meta.counts`) alongside any ranking; (3) sizes:["all"] adds small/micro caps — flag their liquidity risk (market cap is a size proxy, not liquidity); (4) quote `meta.snapshot.score_date` and reuse `next_cursor` to stay on that run. These are stocks matching the given Tapetide Score criteria, NOT investment recommendations. Decision-support only. The Tapetide Score is data analysis, not investment advice. Tapetide is not a SEBI-registered research analyst or investment adviser. Bands are intentionally coarse; small point differences may not be meaningful.
The description explains the capability, when to use it, and what to expect.
Inputs86/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
sizes
Size buckets. Default ["large","mid"]. Use ["all"] for the full scored universe (dominated by micro caps by count — mention the liquidity caveat if you do).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
bands
Score bands to include: "66-plus" (Strong), "55-65" (Good), "45-54" (Average), "37-44" (Weak), "below-37" (Poor) — the keys rows carry in `band`. Omit for all bands. The older keys "70-plus", "60-69", "50-59", "30-49", "below-30" still work and select the same tier by position (70-plus = Strong, i.e. 66+). There is no 80+ band.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
sectors
Sector names as returned in `meta.facets.sectors` (e.g. "Metals & Mining"). Omit for all sectors.
Clear enough to supply this argument.
min_score
Minimum composite score.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
max_score
Maximum composite score.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
min_confidence
Minimum data-confidence, default 75. Lowering it admits stocks with thinner data; the response reports how many the bar excluded.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
q
Substring search on symbol or company name.
Clear enough to supply this argument.
sort
Sort key, default "band" (coarse tiers first — the honest default). "score" is exact composite order; also confidence, market_cap, name.
Clear enough to supply this argument.
order
Direction, default "desc".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Rows per page (default 50, max 100).
Clear enough to supply this argument.
cursor
Pass `meta.next_cursor` from the previous response to get the next page. The run date is embedded in it, so paging stays pinned to one scoring run.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "screen_tapetide_scores",
"title": "Screen & Rank by Tapetide Score",
"description": "List and rank stocks by the Tapetide Score, filtered by size bucket, band, score window, sector, minimum data-confidence and symbol/name search. Rows come back in the server's final order with score, band, pillars, sector, size, market cap and a next-page cursor. USE THIS for 'which large caps score highest', 'show me Strong-band pharma stocks', or any rank/filter-by-Tapetide-Score question — same data and ordering as the tapetide.com ranking page. IMPORTANT, or you will describe the results wrongly: (1) present rows by BAND, never as an ordinal '#1, #2, #3' leaderboard — nothing has ever scored above 77 and neighbouring scores are not meaningfully different; (2) the DEFAULT view is large+mid cap at confidence >= 75, a filtered slice and not the whole market, so state the active filters (`meta.counts`) alongside any ranking; (3) sizes:[\"all\"] adds small/micro caps — flag their liquidity risk (market cap is a size proxy, not liquidity); (4) quote `meta.snapshot.score_date` and reuse `next_cursor` to stay on that run. These are stocks matching the given Tapetide Score criteria, NOT investment recommendations. Decision-support only. The Tapetide Score is data analysis, not investment advice. Tapetide is not a SEBI-registered research analyst or investment adviser. Bands are intentionally coarse; small point differences may not be meaningful.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"q": {
"type": "string",
"description": "Substring search on symbol or company name."
},
"sort": {
"enum": [
"band",
"score",
"confidence",
"market_cap",
"name"
],
"type": "string",
"description": "Sort key, default \"band\" (coarse tiers first — the honest default). \"score\" is exact composite order; also confidence, market_cap, name."
},
"bands": {
"type": "array",
"items": {
"enum": [
"66-plus",
"55-65",
"45-54",
"37-44",
"below-37",
"70-plus",
"60-69",
"50-59",
"30-49",
"below-30"
],
"type": "string"
},
"description": "Score bands to include: \"66-plus\" (Strong), \"55-65\" (Good), \"45-54\" (Average), \"37-44\" (Weak), \"below-37\" (Poor) — the keys rows carry in `band`. Omit for all bands. The older keys \"70-plus\", \"60-69\", \"50-59\", \"30-49\", \"below-30\" still work and select the same tier by position (70-plus = Strong, i.e. 66+). There is no 80+ band."
},
"limit": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Rows per page (default 50, max 100)."
},
"order": {
"enum": [
"asc",
"desc"
],
"type": "string",
"description": "Direction, default \"desc\"."
},
"sizes": {
"type": "array",
"items": {
"enum": [
"large",
"mid",
"small",
"micro",
"all"
],
"type": "string"
},
"description": "Size buckets. Default [\"large\",\"mid\"]. Use [\"all\"] for the full scored universe (dominated by micro caps by count — mention the liquidity caveat if you do)."
},
"cursor": {
"type": "string",
"description": "Pass `meta.next_cursor` from the previous response to get the next page. The run date is embedded in it, so paging stays pinned to one scoring run."
},
"sectors": {
"type": "array",
"items": {
"type": "string"
},
"description": "Sector names as returned in `meta.facets.sectors` (e.g. \"Metals & Mining\"). Omit for all sectors."
},
"max_score": {
"type": "integer",
"maximum": 100,
"minimum": 0,
"description": "Maximum composite score."
},
"min_score": {
"type": "integer",
"maximum": 100,
"minimum": 0,
"description": "Minimum composite score."
},
"min_confidence": {
"type": "integer",
"maximum": 100,
"minimum": 0,
"description": "Minimum data-confidence, default 75. Lowering it admits stocks with thinner data; the response reports how many the bar excluded."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Screen & Rank by Tapetide Score",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Get the INDEX OPTION CHAIN with implied volatility, Greeks, bid/ask and open interest by strike. Use for any option-chain, IV, Greeks, open-interest, PCR or max-pain question — 'show me the NIFTY option chain', 'what is the ATM IV', 'where is max pain', 'put-call ratio', 'OI by strike'. Covers NIFTY, BANKNIFTY, FINNIFTY, MIDCPNIFTY ONLY — we do not collect a chain for individual stocks, so for a stock-option question say the chain covers index options only rather than implying we have no options data at all; get_option_iv_history DOES cover ~556 underlyings including stocks. IMPORTANT: this is an END-OF-DAY STAMPED snapshot, not a streaming live tick. Read `snapshot_ts` and state it (e.g. 'as of the 7 Aug close') — never imply an intraday real-time quote. `iv_pct` and `atm_iv_pct` are PERCENT (10.87 means 10.87%); `atm_iv_change` is percentage POINTS vs the prior session. NULLS ARE UNAVAILABLE, NEVER ZERO: a leg flagged `iv_unsolved` has null IV and Greeks (reason in `iv_status`), `illiquid` means no OI/volume so its premium is indicative only, and `pcr_undefined` means the put/call ratio cannot be computed. Render these as '—'; never state a 0% IV, a 0 delta or a PCR of 0. Also read `atm_offset` (strike steps from ATM) and `available_expiries`. Present the chain as data: report the numbers and what they describe. Do NOT recommend a strike, a strategy, or a direction to trade.
The description explains the capability, when to use it, and what to expect.
Inputs70/100
Resolve the mismatch between this description and its schema constraints.
Resolve the mismatch between this description and its schema constraints.
expiry
Expiry as YYYY-MM-DD. Omit for the nearest expiry in the snapshot.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
strikes
Strikes to return EACH SIDE of ATM (default 11, max 25)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Clear enough to supply this argument.
identifier
Alias for `symbol`.
Clear enough to supply this argument.
Annotations100/100
All four behavior hints are declared.
{
"title": "Index Option Chain (IV, Greeks, OI by strike)",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_option_chain",
"title": "Index Option Chain (IV, Greeks, OI by strike)",
"description": "Get the INDEX OPTION CHAIN with implied volatility, Greeks, bid/ask and open interest by strike. Use for any option-chain, IV, Greeks, open-interest, PCR or max-pain question — 'show me the NIFTY option chain', 'what is the ATM IV', 'where is max pain', 'put-call ratio', 'OI by strike'. Covers NIFTY, BANKNIFTY, FINNIFTY, MIDCPNIFTY ONLY — we do not collect a chain for individual stocks, so for a stock-option question say the chain covers index options only rather than implying we have no options data at all; get_option_iv_history DOES cover ~556 underlyings including stocks. IMPORTANT: this is an END-OF-DAY STAMPED snapshot, not a streaming live tick. Read `snapshot_ts` and state it (e.g. 'as of the 7 Aug close') — never imply an intraday real-time quote. `iv_pct` and `atm_iv_pct` are PERCENT (10.87 means 10.87%); `atm_iv_change` is percentage POINTS vs the prior session. NULLS ARE UNAVAILABLE, NEVER ZERO: a leg flagged `iv_unsolved` has null IV and Greeks (reason in `iv_status`), `illiquid` means no OI/volume so its premium is indicative only, and `pcr_undefined` means the put/call ratio cannot be computed. Render these as '—'; never state a 0% IV, a 0 delta or a PCR of 0. Also read `atm_offset` (strike steps from ATM) and `available_expiries`. Present the chain as data: report the numbers and what they describe. Do NOT recommend a strike, a strategy, or a direction to trade.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"expiry": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Expiry as YYYY-MM-DD. Omit for the nearest expiry in the snapshot."
},
"symbol": {
"type": "string",
"description": "REQUIRED. Index underlying: NIFTY | BANKNIFTY | FINNIFTY | MIDCPNIFTY (index options only)."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"strikes": {
"type": "number",
"description": "Strikes to return EACH SIDE of ATM (default 11, max 25)"
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Index Option Chain (IV, Greeks, OI by strike)",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Get the HISTORICAL option-analytics time series for an underlying — ATM implied volatility, IV rank, IV percentile, realised vol, put-call ratio (OI and volume), max pain and 25-delta skew, one point per session. Use for 'is IV high right now', 'IV rank of RELIANCE', 'has volatility been rising', or any volatility-regime / IV-vs-realised comparison. Covers ~556 underlyings INCLUDING individual stocks (unlike get_option_chain, which is index-only). UNITS: every IV field is a PERCENT (10.55 means 10.55% annualised) — never multiply by 100 again. `iv_rank_pct` and `iv_percentile_pct` are percents too, not 0-1 scores, and they are DIFFERENT measures: rank is position in the trailing high-low band, percentile is the share of sessions below the current reading. Read `bar_interval` — ranges of 2y+ are rolled up WEEKLY, so counting points as trading days will be wrong; one call returns at most the 400 most recent bars, so quote the `from_date`/`to_date` returned rather than assuming full history. The response also states its own `coverage` and flags `spot_is_proxy` — respect both. Report the numbers and what they describe. Do NOT recommend a trade, a strike, or a volatility position.
The description explains the capability, when to use it, and what to expect.
Inputs69/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. Underlying symbol — a stock like "RELIANCE" or an index like "NIFTY".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Explain the meaning of this value, not just its name.
identifier
Alias for `symbol`.
Explain the meaning of this value, not just its name.
Annotations100/100
All four behavior hints are declared.
{
"title": "Option IV History (ATM IV, IV rank, PCR series)",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_option_iv_history",
"title": "Option IV History (ATM IV, IV rank, PCR series)",
"description": "Get the HISTORICAL option-analytics time series for an underlying — ATM implied volatility, IV rank, IV percentile, realised vol, put-call ratio (OI and volume), max pain and 25-delta skew, one point per session. Use for 'is IV high right now', 'IV rank of RELIANCE', 'has volatility been rising', or any volatility-regime / IV-vs-realised comparison. Covers ~556 underlyings INCLUDING individual stocks (unlike get_option_chain, which is index-only). UNITS: every IV field is a PERCENT (10.55 means 10.55% annualised) — never multiply by 100 again. `iv_rank_pct` and `iv_percentile_pct` are percents too, not 0-1 scores, and they are DIFFERENT measures: rank is position in the trailing high-low band, percentile is the share of sessions below the current reading. Read `bar_interval` — ranges of 2y+ are rolled up WEEKLY, so counting points as trading days will be wrong; one call returns at most the 400 most recent bars, so quote the `from_date`/`to_date` returned rather than assuming full history. The response also states its own `coverage` and flags `spot_is_proxy` — respect both. Report the numbers and what they describe. Do NOT recommend a trade, a strike, or a volatility position.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"range": {
"enum": [
"1m",
"3m",
"6m",
"1y",
"2y",
"5y",
"max"
],
"type": "string",
"description": "Lookback window (default 1y). 2y and longer return WEEKLY bars — read `bar_interval`."
},
"symbol": {
"type": "string",
"description": "REQUIRED. Underlying symbol — a stock like \"RELIANCE\" or an index like \"NIFTY\"."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Option IV History (ATM IV, IV rank, PCR series)",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Rank NSE indices by RETURN over recent completed weeks or months, using official NSE index closing levels. Returns per-period % plus cumulative % for each index, sorted best-to-worst. Covers ~140 indices: all sectoral (IT, Bank, Auto, Pharma, FMCG, Metal, Realty, Energy, Oil & Gas, PSU Bank, Private Bank, Media, Healthcare, Consumer Durables, Power, Insurance, Telecom, Chemicals, Cement, Capital Goods, NBFC, Retail and more), plus broad market/size, thematic and strategy/factor indices. USE THIS for 'rank sectoral indices by 3-week return', 'which sector performed best last month', 'top gaining sectors', or weekly close-to-close index returns — do NOT compute a sector return from its constituents, which is only an approximation. Only COMPLETED periods are counted; the in-progress week/month is excluded.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
periods
How many COMPLETED periods to measure (1-12, e.g. 3 = last 3 completed weeks)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
granularity
Period length: 'week' = weekly close-to-close, 'month' = monthly
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
category
Restrict to one index family. Use 'sectoral' for sector rankings — that is almost always what a 'which sector' question means. Omit for all indices.
Clear enough to supply this argument.
index_names
Explicit index names, e.g. ['Nifty IT','Nifty Bank']. Overrides category. Matched case-insensitively against the catalog.
Clear enough to supply this argument.
limit
Max indices to return after ranking (1-50)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
order
'gainers' = best cumulative first, 'losers' = worst first
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_index_performance",
"title": "Index Performance Ranking",
"description": "Rank NSE indices by RETURN over recent completed weeks or months, using official NSE index closing levels. Returns per-period % plus cumulative % for each index, sorted best-to-worst. Covers ~140 indices: all sectoral (IT, Bank, Auto, Pharma, FMCG, Metal, Realty, Energy, Oil & Gas, PSU Bank, Private Bank, Media, Healthcare, Consumer Durables, Power, Insurance, Telecom, Chemicals, Cement, Capital Goods, NBFC, Retail and more), plus broad market/size, thematic and strategy/factor indices. USE THIS for 'rank sectoral indices by 3-week return', 'which sector performed best last month', 'top gaining sectors', or weekly close-to-close index returns — do NOT compute a sector return from its constituents, which is only an approximation. Only COMPLETED periods are counted; the in-progress week/month is excluded.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "number",
"default": 10,
"description": "Max indices to return after ranking (1-50)"
},
"order": {
"enum": [
"gainers",
"losers"
],
"type": "string",
"default": "gainers",
"description": "'gainers' = best cumulative first, 'losers' = worst first"
},
"periods": {
"type": "number",
"default": 3,
"description": "How many COMPLETED periods to measure (1-12, e.g. 3 = last 3 completed weeks)"
},
"category": {
"enum": [
"sectoral",
"broad",
"thematic",
"strategy",
"volatility"
],
"type": "string",
"description": "Restrict to one index family. Use 'sectoral' for sector rankings — that is almost always what a 'which sector' question means. Omit for all indices."
},
"granularity": {
"enum": [
"week",
"month"
],
"type": "string",
"default": "week",
"description": "Period length: 'week' = weekly close-to-close, 'month' = monthly"
},
"index_names": {
"type": "array",
"items": {
"type": "string"
},
"description": "Explicit index names, e.g. ['Nifty IT','Nifty Bank']. Overrides category. Matched case-insensitively against the catalog."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Index Performance Ranking",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Get the historical LEVEL series (OHLC + PE/PB/dividend yield) for a single NSE INDEX — Nifty 50, Nifty Bank, Nifty IT, Nifty Oil & Gas, India VIX, and ~140 more. Official NSE index data. Use for 'what did Nifty IT close at on <date>', 'Nifty Bank level history', 'India VIX over the last month', or index valuation trend. This is the INDEX counterpart of get_price_history (which handles individual stocks only). To rank or compare MULTIPLE indices by return, use get_index_performance instead. Over the size limit the newest bars are kept (data.page); while meta.window.has_more, pass meta.window.next_cursor as `end_date`. count/from/change_pct cover the whole window, ending at `end_date` when given.
The description explains the capability, when to use it, and what to expect.
Inputs72/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
index_name
REQUIRED. Index name, e.g. 'Nifty 50', 'Nifty IT', 'Nifty Oil & Gas'
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
index
Alias for `index_name`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
Alias for `index_name`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
slug
Alias for `index_name`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
index_slug
Alias for `index_name`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
index_symbol
Alias for `index_name`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
index_identifier
Alias for `index_name`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
identifier
Alias for `index_name`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
index_code
Alias for `index_name`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
code
Alias for `index_name`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
interval
LOOKBACK window, one of 1m, 3m, 6m, 1y, 2y, max (default 3m). Bars are daily up to 1y, weekly for 2y/max. Not a bar size: intraday is not served.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
range
Alias for `interval`.
Clear enough to supply this argument.
days
Alias for `interval`: a lookback in calendar days, mapped to the smallest served window that covers it.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_index_history",
"title": "Index Level History",
"description": "Get the historical LEVEL series (OHLC + PE/PB/dividend yield) for a single NSE INDEX — Nifty 50, Nifty Bank, Nifty IT, Nifty Oil & Gas, India VIX, and ~140 more. Official NSE index data. Use for 'what did Nifty IT close at on <date>', 'Nifty Bank level history', 'India VIX over the last month', or index valuation trend. This is the INDEX counterpart of get_price_history (which handles individual stocks only). To rank or compare MULTIPLE indices by return, use get_index_performance instead. Over the size limit the newest bars are kept (data.page); while meta.window.has_more, pass meta.window.next_cursor as `end_date`. count/from/change_pct cover the whole window, ending at `end_date` when given.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"code": {
"type": [
"string",
"number"
],
"description": "Alias for `index_name`."
},
"days": {
"type": [
"number",
"string"
],
"description": "Alias for `interval`: a lookback in calendar days, mapped to the smallest served window that covers it."
},
"slug": {
"type": "string",
"description": "Alias for `index_name`."
},
"index": {
"type": "string",
"description": "Alias for `index_name`."
},
"range": {
"type": "string",
"description": "Alias for `interval`."
},
"symbol": {
"type": "string",
"description": "Alias for `index_name`."
},
"end_date": {
"type": "string",
"description": "Inclusive end, YYYY-MM-DD (default: latest). Paging cursor."
},
"interval": {
"type": "string",
"description": "LOOKBACK window, one of 1m, 3m, 6m, 1y, 2y, max (default 3m). Bars are daily up to 1y, weekly for 2y/max. Not a bar size: intraday is not served."
},
"identifier": {
"type": "string",
"description": "Alias for `index_name`."
},
"index_code": {
"type": [
"string",
"number"
],
"description": "Alias for `index_name`."
},
"index_name": {
"type": "string",
"description": "REQUIRED. Index name, e.g. 'Nifty 50', 'Nifty IT', 'Nifty Oil & Gas'"
},
"index_slug": {
"type": "string",
"description": "Alias for `index_name`."
},
"index_symbol": {
"type": "string",
"description": "Alias for `index_name`."
},
"index_identifier": {
"type": "string",
"description": "Alias for `index_name`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Index Level History",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
Name the specific action and subject instead of using a generic label such as ‘manage’ or ‘tool’.
Description96/100
Indian mutual fund scheme by scheme code, ISIN or name (also old names, typos). A sure match returns the plan (fund, house, category, plan/option, ISINs, latest NAV), trailing and calendar-year returns from its NAVs, current expense ratio and its changes, the fund's profile (objective, benchmark, riskometer, exit load, minimums, managers), a fund-level snapshot (AUM, returns vs benchmark), risk or tracking figures where available, volatility, Sharpe and Sortino computed from NAVs, its latest portfolio month and other plans. Else ranked scheme codes, flagged when uncertain. Active and closed schemes; returns are in percent, 3y+ annualised.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
query
Scheme code, ISIN, or name as written, e.g. "parag flexi cap direct growth".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_mutual_fund",
"title": "Mutual Fund",
"description": "Indian mutual fund scheme by scheme code, ISIN or name (also old names, typos). A sure match returns the plan (fund, house, category, plan/option, ISINs, latest NAV), trailing and calendar-year returns from its NAVs, current expense ratio and its changes, the fund's profile (objective, benchmark, riskometer, exit load, minimums, managers), a fund-level snapshot (AUM, returns vs benchmark), risk or tracking figures where available, volatility, Sharpe and Sortino computed from NAVs, its latest portfolio month and other plans. Else ranked scheme codes, flagged when uncertain. Active and closed schemes; returns are in percent, 3y+ annualised.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "Scheme code, ISIN, or name as written, e.g. \"parag flexi cap direct growth\"."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Mutual Fund",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description85/100
Daily NAV history of one mutual fund plan by scheme code (INR per unit, from as early as 1986). Long ranges return period-end NAVs (weekly, monthly or quarterly) so the series fits; `interval` forces one (newest 300 points at most).
The description explains the capability, when to use it, and what to expect.
Inputs81/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
scheme_code
Scheme code, e.g. "122639".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
from
YYYY-MM-DD; default one year before `to`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
to
YYYY-MM-DD; default the latest NAV. A holiday gives the last NAV before it.
Clear enough to supply this argument.
interval
Sampling; default: the finest that fits.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Annotations100/100
All four behavior hints are declared.
{
"title": "Mutual Fund NAV History",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_mutual_fund_nav_history",
"title": "Mutual Fund NAV History",
"description": "Daily NAV history of one mutual fund plan by scheme code (INR per unit, from as early as 1986). Long ranges return period-end NAVs (weekly, monthly or quarterly) so the series fits; `interval` forces one (newest 300 points at most).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"scheme_code"
],
"properties": {
"to": {
"type": "string",
"description": "YYYY-MM-DD; default the latest NAV. A holiday gives the last NAV before it."
},
"from": {
"type": "string",
"description": "YYYY-MM-DD; default one year before `to`."
},
"interval": {
"enum": [
"daily",
"weekly",
"monthly",
"quarterly"
],
"type": "string",
"description": "Sampling; default: the finest that fits."
},
"scheme_code": {
"type": "string",
"pattern": "^[1-9]\\d{0,8}$",
"description": "Scheme code, e.g. \"122639\"."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Mutual Fund NAV History",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description86/100
A fund's month-end portfolio: every line, largest value (INR crore) first, as compact rows (weight, ISIN, symbol, standard and printed industry or rating, rating agency, cash kind) paged by offset; net assets; a summary (asset classes, cash, top 10, industries, market-cap split). Start year varies by house. By scheme_code, or a fund's name: its linked portfolio (`link` says confirmed or inferred). Else name words match statements, each at its newest in 13 months; several list house and portfolio_code. `compare`: bought and sold since a month. `stock`: funds holding a stock, with scheme codes.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
scheme_code
Scheme code of any plan of the fund, e.g. "122639".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
fund
Scheme name words, e.g. "parag flexi cap".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
house
Fund-house key from a previous match, e.g. "ppfas".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
portfolio_code
Portfolio code from a previous match.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
month
YYYY-MM. Default: the newest month linked to the fund.
Clear enough to supply this argument.
top
Rows per page (default 25; compare/stock max 100).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
offset
A previous page's next_offset.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
statement_key
A previous page's statement_key.
Explain the meaning of this value, not just its name.
compare
"previous" or YYYY-MM: changes since then.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
stock
Symbol or ISIN: funds holding it.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_mutual_fund_portfolio",
"title": "Mutual Fund Portfolio",
"description": "A fund's month-end portfolio: every line, largest value (INR crore) first, as compact rows (weight, ISIN, symbol, standard and printed industry or rating, rating agency, cash kind) paged by offset; net assets; a summary (asset classes, cash, top 10, industries, market-cap split). Start year varies by house. By scheme_code, or a fund's name: its linked portfolio (`link` says confirmed or inferred). Else name words match statements, each at its newest in 13 months; several list house and portfolio_code. `compare`: bought and sold since a month. `stock`: funds holding a stock, with scheme codes.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"top": {
"type": "integer",
"maximum": 500,
"minimum": 1,
"description": "Rows per page (default 25; compare/stock max 100)."
},
"fund": {
"type": "string",
"maxLength": 80,
"minLength": 2,
"description": "Scheme name words, e.g. \"parag flexi cap\"."
},
"house": {
"type": "string",
"maxLength": 40,
"description": "Fund-house key from a previous match, e.g. \"ppfas\"."
},
"month": {
"type": "string",
"description": "YYYY-MM. Default: the newest month linked to the fund."
},
"stock": {
"type": "string",
"maxLength": 40,
"minLength": 2,
"description": "Symbol or ISIN: funds holding it."
},
"offset": {
"type": "integer",
"maximum": 100000,
"minimum": 0,
"description": "A previous page's next_offset."
},
"compare": {
"type": "string",
"pattern": "^(previous|\\d{4}-\\d{2})$",
"description": "\"previous\" or YYYY-MM: changes since then."
},
"scheme_code": {
"type": "string",
"pattern": "^[1-9]\\d{0,8}$",
"description": "Scheme code of any plan of the fund, e.g. \"122639\"."
},
"statement_key": {
"type": "string",
"maxLength": 16,
"description": "A previous page's statement_key."
},
"portfolio_code": {
"type": "string",
"maxLength": 128,
"description": "Portfolio code from a previous match."
}
},
"additionalProperties": true
},
"annotations": {
"title": "Mutual Fund Portfolio",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description90/100
Rank, filter or compare Indian mutual funds: one row per fund with category, benchmark, 1/3/5y returns vs benchmark, base expense ratio (and all-in), average AUM, first NAV date. Filter and sort by those, or compare up to 10 scheme_codes. One category adds its quartiles. Past returns, not advice.
The description explains the capability, when to use it, and what to expect.
Inputs52/100
8 of 11 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
category
Key or name, e.g. "flexi-cap", "Liquid"; unknown lists all.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
fund_house
e.g. "HDFC Mutual Fund".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
benchmark
e.g. "Nifty 50 TRI".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
plan
Default direct.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
first_nav_from
YYYY-MM-DD
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
first_nav_to
Not provided
Missing description. Explain what this value means and how to supply it.
scheme_codes
Plans to compare, alone.
Explain the meaning of this value, not just its name.
sort
Not provided
Missing description. Explain what this value means and how to supply it.
order
Not provided
Missing description. Explain what this value means and how to supply it.
limit
Default 20.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
cursor
A previous page's next_cursor.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description87/100
One IPO by name or slug: timetable to refund, demat credit and listing; lots and amounts per category; shares reserved incl. anchor and market maker; anchor book with lock-in dates; latest bids per category (times, shares, INR crore, time); latest grey market premium (unofficial) with sauda; KPIs, financials, objects, peers. Application counts are not available.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
query
Company name or slug, e.g. "tonbo imaging".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description99/100
Get the split/bonus adjustment-factor timeline for a stock, so a raw (unadjusted) price series can be reconstructed from the adjusted one. Returns per-event factor and cumulative factor with ex-dates, plus the reconstruction formula in meta. USE THIS when a price move looks impossibly large and you need to know whether it was a corporate action rather than a real return, or when the user asks for raw/unadjusted prices, or asks how to adjust for splits and bonuses. CRITICAL: the response also carries `unquantified_events` — rights issues and demergers that are KNOWN but have NO reliable numeric factor (a rights adjustment needs the subscription price; a demerger is not a single number). Never invent a factor for those; tell the user those ex-dates should be excluded or treated with caution. NOTE: `data` has split/bonus factors; rights factors are on REST corporate-adjustments. PRICE-return, not total-return.
The description explains the capability, when to use it, and what to expect.
Inputs68/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. The stock symbol, e.g. "RELIANCE" or "TRENT".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
identifier
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_adjustment_factors",
"title": "Price Adjustment Factors",
"description": "Get the split/bonus adjustment-factor timeline for a stock, so a raw (unadjusted) price series can be reconstructed from the adjusted one. Returns per-event factor and cumulative factor with ex-dates, plus the reconstruction formula in meta. USE THIS when a price move looks impossibly large and you need to know whether it was a corporate action rather than a real return, or when the user asks for raw/unadjusted prices, or asks how to adjust for splits and bonuses. CRITICAL: the response also carries `unquantified_events` — rights issues and demergers that are KNOWN but have NO reliable numeric factor (a rights adjustment needs the subscription price; a demerger is not a single number). Never invent a factor for those; tell the user those ex-dates should be excluded or treated with caution. NOTE: `data` has split/bonus factors; rights factors are on REST corporate-adjustments. PRICE-return, not total-return.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"symbol": {
"type": "string",
"description": "REQUIRED. The stock symbol, e.g. \"RELIANCE\" or \"TRENT\"."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Price Adjustment Factors",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
For every CALENDAR day in a lookback window, get why a price is or is not present: `traded`, `weekend`, `holiday`, `pre_listing`, `delisted`, or `no_print`. USE THIS when a price series has gaps and the user needs to know whether a missing day was a market holiday, a suspension, a pre-listing date, or genuinely missing data — and ESPECIALLY before computing returns over a gappy series. A missing price is NOT a zero return: `no_print` means a listed trading day with no print and should be treated as not-a-return (carry forward or mask), never as 0%. HONESTY LIMITS in the response's `classification_limits`: `no_print` deliberately does NOT distinguish an illiquid no-trade from a suspension from missing data (no per-day suspension feed exists, so a specific reason would be fabricated), and `pre_listing` can only be asserted where a listing date is known — its absence is not evidence the stock was trading.
The description explains the capability, when to use it, and what to expect.
Inputs81/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. The stock symbol, e.g. "TRENT".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
days
Calendar days to look back (default 365, max 10000)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Clear enough to supply this argument.
identifier
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_observation_status",
"title": "Per-Day Observation Status",
"description": "For every CALENDAR day in a lookback window, get why a price is or is not present: `traded`, `weekend`, `holiday`, `pre_listing`, `delisted`, or `no_print`. USE THIS when a price series has gaps and the user needs to know whether a missing day was a market holiday, a suspension, a pre-listing date, or genuinely missing data — and ESPECIALLY before computing returns over a gappy series. A missing price is NOT a zero return: `no_print` means a listed trading day with no print and should be treated as not-a-return (carry forward or mask), never as 0%. HONESTY LIMITS in the response's `classification_limits`: `no_print` deliberately does NOT distinguish an illiquid no-trade from a suspension from missing data (no per-day suspension feed exists, so a specific reason would be fabricated), and `pre_listing` can only be asserted where a listing date is known — its absence is not evidence the stock was trading.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"days": {
"type": "number",
"default": 365,
"description": "Calendar days to look back (default 365, max 10000)"
},
"symbol": {
"type": "string",
"description": "REQUIRED. The stock symbol, e.g. \"TRENT\"."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Per-Day Observation Status",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description99/100
Was a stock a constituent of an index on a specific historical date? Returns a FOUR-STATE answer, never a bare yes/no: `present` (proven in range), `uncertain` (inside an unobserved bracket around a join/leave — plausible but NOT proven), `absent` (proven not a member, within coverage), or `out_of_coverage` (outside the observed window — we cannot answer). USE THIS for any 'was X in the Nifty 50/500 on <date>' question, and for point-in-time universe construction or survivorship-bias-aware backtests. Do NOT infer historical membership from today's constituent list — that is exactly the survivorship bias this tool exists to avoid. REPORT UNCERTAINTY HONESTLY: treat `uncertain` and `out_of_coverage` as NOT tradeable signal and say so; never silently collapse either into `absent`. The response states its own `meta.coverage` window plus `meta.freshness.lag_days` — trust answers only up to `coverage.answerable_through`.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
index
REQUIRED. Index name, e.g. "Nifty 50", "Nifty 500", "Nifty Midcap 150".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. The stock symbol, e.g. "TRENT".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
date
As-of date, YYYY-MM-DD. Default: the latest covered date.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
identifier
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_index_membership_asof",
"title": "Index Membership As-Of a Date",
"description": "Was a stock a constituent of an index on a specific historical date? Returns a FOUR-STATE answer, never a bare yes/no: `present` (proven in range), `uncertain` (inside an unobserved bracket around a join/leave — plausible but NOT proven), `absent` (proven not a member, within coverage), or `out_of_coverage` (outside the observed window — we cannot answer). USE THIS for any 'was X in the Nifty 50/500 on <date>' question, and for point-in-time universe construction or survivorship-bias-aware backtests. Do NOT infer historical membership from today's constituent list — that is exactly the survivorship bias this tool exists to avoid. REPORT UNCERTAINTY HONESTLY: treat `uncertain` and `out_of_coverage` as NOT tradeable signal and say so; never silently collapse either into `absent`. The response states its own `meta.coverage` window plus `meta.freshness.lag_days` — trust answers only up to `coverage.answerable_through`.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"date": {
"type": "string",
"description": "As-of date, YYYY-MM-DD. Default: the latest covered date."
},
"index": {
"type": "string",
"description": "REQUIRED. Index name, e.g. \"Nifty 50\", \"Nifty 500\", \"Nifty Midcap 150\"."
},
"symbol": {
"type": "string",
"description": "REQUIRED. The stock symbol, e.g. \"TRENT\"."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Index Membership As-Of a Date",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description99/100
Resolve a historical symbol or ISIN to the company that held it ON a given date. USE THIS when working with old data whose ticker may since have been renamed, reused, or reassigned — e.g. a 2018 holdings file, an old research note, or a backtest that must not treat one company as two securities (or worse, merge two different companies because a ticker was recycled after a delisting). Returns `present` | `uncertain` | `not_found` | `out_of_coverage` with certainty ranges; each match names the company by its latest known `symbol` and `isin`, which the other stock tools take. `uncertain` means the date falls in an open bracket around a rename/ISIN change — quarantine it rather than asserting the mapping. The response states its own coverage window; a date outside it returns `out_of_coverage` and must not be reported as 'no such symbol'.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
value
REQUIRED. The identifier value, e.g. "TRENT" or "INE849A01020".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
identifier
Alias for `value`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
query
Alias for `value`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
kind
Which identifier kind `value` is (default nse_symbol)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
date
As-of date, YYYY-MM-DD. Defaults to today (IST) when omitted.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Annotations100/100
All four behavior hints are declared.
{
"title": "Resolve a Symbol/ISIN As-Of a Date",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "resolve_identifier_asof",
"title": "Resolve a Symbol/ISIN As-Of a Date",
"description": "Resolve a historical symbol or ISIN to the company that held it ON a given date. USE THIS when working with old data whose ticker may since have been renamed, reused, or reassigned — e.g. a 2018 holdings file, an old research note, or a backtest that must not treat one company as two securities (or worse, merge two different companies because a ticker was recycled after a delisting). Returns `present` | `uncertain` | `not_found` | `out_of_coverage` with certainty ranges; each match names the company by its latest known `symbol` and `isin`, which the other stock tools take. `uncertain` means the date falls in an open bracket around a rename/ISIN change — quarantine it rather than asserting the mapping. The response states its own coverage window; a date outside it returns `out_of_coverage` and must not be reported as 'no such symbol'.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"date": {
"type": "string",
"description": "As-of date, YYYY-MM-DD. Defaults to today (IST) when omitted."
},
"kind": {
"enum": [
"nse_symbol",
"isin"
],
"type": "string",
"default": "nse_symbol",
"description": "Which identifier kind `value` is (default nse_symbol)"
},
"query": {
"type": "string",
"description": "Alias for `value`."
},
"value": {
"type": "string",
"description": "REQUIRED. The identifier value, e.g. \"TRENT\" or \"INE849A01020\"."
},
"identifier": {
"type": "string",
"description": "Alias for `value`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Resolve a Symbol/ISIN As-Of a Date",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description89/100
The REVERSE of resolve_identifier_asof: given a company's `symbol` and a date, return which symbol and ISIN that company held at that time. USE THIS to label historical output correctly — e.g. reporting a 2019 backtest position under the ticker it actually traded as then, rather than its current name. Also useful for explaining a rename to a user who is confused why a symbol they remember no longer resolves. Pass the symbol the company trades as today (resolve_identifier_asof maps an old ticker to it). Coverage bounds are stated in the response — outside them the answer is `out_of_coverage`, not 'no identifiers'.
The description explains the capability, when to use it, and what to expect.
Inputs80/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. The company's current stock symbol, e.g. "TRENT".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
stock_id
Deprecated. Use `symbol`.
Explain the meaning of this value, not just its name.
date
As-of date, YYYY-MM-DD. Defaults to today (IST) when omitted.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Clear enough to supply this argument.
identifier
Alias for `symbol`.
Clear enough to supply this argument.
Annotations100/100
All four behavior hints are declared.
{
"title": "Identifiers Held By a Stock As-Of a Date",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_identifiers_asof",
"title": "Identifiers Held By a Stock As-Of a Date",
"description": "The REVERSE of resolve_identifier_asof: given a company's `symbol` and a date, return which symbol and ISIN that company held at that time. USE THIS to label historical output correctly — e.g. reporting a 2019 backtest position under the ticker it actually traded as then, rather than its current name. Also useful for explaining a rename to a user who is confused why a symbol they remember no longer resolves. Pass the symbol the company trades as today (resolve_identifier_asof maps an old ticker to it). Coverage bounds are stated in the response — outside them the answer is `out_of_coverage`, not 'no identifiers'.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"date": {
"type": "string",
"description": "As-of date, YYYY-MM-DD. Defaults to today (IST) when omitted."
},
"symbol": {
"type": "string",
"description": "REQUIRED. The company's current stock symbol, e.g. \"TRENT\"."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"stock_id": {
"type": "integer",
"description": "Deprecated. Use `symbol`."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Identifiers Held By a Stock As-Of a Date",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
List the NAMED shareholders of a stock for one quarter: each promoter-group entity and each public shareholder holding 1% or more, with shares, % held, pledged/locked shares, investor_type and a stable investor_id. `by_bucket` sums named holders per investor type (not category totals). `meta.available_quarters` lists every quarter on file. Coverage: promoter-group entities are always named; public shareholders are named only at 1% or more, so a public-side 'exit' can mean the holder dropped below 1% (see listed_from/listed_to).
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. Stock symbol, e.g. "RELIANCE".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Clear enough to supply this argument.
identifier
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
quarter
Quarter (default latest): "latest", a calendar quarter "YYYY-Qn" (Q1=Mar-31 … Q4=Dec-31), or the quarter-end date YYYY-MM-DD.
Clear enough to supply this argument.
side
promoter | public | all (default all).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
investor_type
Filter to one investor type, e.g. mutual_fund, insurance, fpi.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_named_holders",
"title": "Named Shareholders",
"description": "List the NAMED shareholders of a stock for one quarter: each promoter-group entity and each public shareholder holding 1% or more, with shares, % held, pledged/locked shares, investor_type and a stable investor_id. `by_bucket` sums named holders per investor type (not category totals). `meta.available_quarters` lists every quarter on file. Coverage: promoter-group entities are always named; public shareholders are named only at 1% or more, so a public-side 'exit' can mean the holder dropped below 1% (see listed_from/listed_to).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"side": {
"enum": [
"promoter",
"public",
"all"
],
"type": "string",
"description": "promoter | public | all (default all)."
},
"symbol": {
"type": "string",
"description": "REQUIRED. Stock symbol, e.g. \"RELIANCE\"."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"quarter": {
"type": "string",
"description": "Quarter (default latest): \"latest\", a calendar quarter \"YYYY-Qn\" (Q1=Mar-31 … Q4=Dec-31), or the quarter-end date YYYY-MM-DD."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
},
"investor_type": {
"enum": [
"promoter",
"mutual_fund",
"insurance",
"pension_fund",
"fpi",
"aif",
"venture_capital",
"sovereign_wealth_fund",
"bank",
"nbfc",
"other_financial_institution",
"government",
"iepf",
"fdi",
"nri_foreign_individual",
"corporate",
"individual",
"unclaimed_suspense",
"other"
],
"type": "string",
"description": "Filter to one investor type, e.g. mutual_fund, insurance, fpi."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Named Shareholders",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description90/100
One holder's position in one stock across every quarter on file, newest first. `holder` is an investor_id from get_named_holders or a display name (normalized server-side). A quarter on file where the holder is not named returns `listed: false`; quarters not on file are absent. A holder that moved between promoter and public appears twice in that quarter.
The description explains the capability, when to use it, and what to expect.
Inputs69/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. Stock symbol, e.g. "RELIANCE".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
identifier
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
holder
REQUIRED. investor_id or holder name, e.g. "lifeinsurancecorporationofindia".
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_named_holder_history",
"title": "Named Shareholder History",
"description": "One holder's position in one stock across every quarter on file, newest first. `holder` is an investor_id from get_named_holders or a display name (normalized server-side). A quarter on file where the holder is not named returns `listed: false`; quarters not on file are absent. A holder that moved between promoter and public appears twice in that quarter.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"holder": {
"type": "string",
"description": "REQUIRED. investor_id or holder name, e.g. \"lifeinsurancecorporationofindia\"."
},
"symbol": {
"type": "string",
"description": "REQUIRED. Stock symbol, e.g. \"RELIANCE\"."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Named Shareholder History",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Quarter-over-quarter diff of a stock's named shareholders: entry, exit, increased, reduced, unchanged per holder, with share and % deltas, renames and promoter/public reclassifications flagged. Share counts are adjusted for splits and bonuses between the two quarters (`meta.share_adjustment`). `from` defaults to the quarter on file immediately before `to`; `meta.gap_quarters` > 0 means the diff spans more than one quarter. `summary` gives counts per status. Coverage: promoter-group entities are always named; public shareholders are named only at 1% or more, so a public-side 'exit' can mean the holder dropped below 1% (see listed_from/listed_to).
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. Stock symbol, e.g. "RELIANCE".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Clear enough to supply this argument.
identifier
Alias for `symbol`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
from
Base quarter (default: the quarter on file before `to`): "latest", a calendar quarter "YYYY-Qn" (Q1=Mar-31 … Q4=Dec-31), or the quarter-end date YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
to
Target quarter (default latest): "latest", a calendar quarter "YYYY-Qn" (Q1=Mar-31 … Q4=Dec-31), or the quarter-end date YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
side
promoter | public | all (default all).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
status
Only these statuses, e.g. ["entry","exit"].
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
include_unchanged
Include unchanged holders (default false).
Explain the meaning of this value, not just its name.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_named_holder_changes",
"title": "Named Shareholder Changes",
"description": "Quarter-over-quarter diff of a stock's named shareholders: entry, exit, increased, reduced, unchanged per holder, with share and % deltas, renames and promoter/public reclassifications flagged. Share counts are adjusted for splits and bonuses between the two quarters (`meta.share_adjustment`). `from` defaults to the quarter on file immediately before `to`; `meta.gap_quarters` > 0 means the diff spans more than one quarter. `summary` gives counts per status. Coverage: promoter-group entities are always named; public shareholders are named only at 1% or more, so a public-side 'exit' can mean the holder dropped below 1% (see listed_from/listed_to).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"to": {
"type": "string",
"description": "Target quarter (default latest): \"latest\", a calendar quarter \"YYYY-Qn\" (Q1=Mar-31 … Q4=Dec-31), or the quarter-end date YYYY-MM-DD."
},
"from": {
"type": "string",
"description": "Base quarter (default: the quarter on file before `to`): \"latest\", a calendar quarter \"YYYY-Qn\" (Q1=Mar-31 … Q4=Dec-31), or the quarter-end date YYYY-MM-DD."
},
"side": {
"enum": [
"promoter",
"public",
"all"
],
"type": "string",
"description": "promoter | public | all (default all)."
},
"status": {
"type": "array",
"items": {
"enum": [
"entry",
"exit",
"increased",
"reduced",
"unchanged"
],
"type": "string"
},
"maxItems": 5,
"description": "Only these statuses, e.g. [\"entry\",\"exit\"]."
},
"symbol": {
"type": "string",
"description": "REQUIRED. Stock symbol, e.g. \"RELIANCE\"."
},
"ticker": {
"type": "string",
"description": "Alias for `symbol`."
},
"identifier": {
"type": "string",
"description": "Alias for `symbol`."
},
"include_unchanged": {
"type": "boolean",
"description": "Include unchanged holders (default false)."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Named Shareholder Changes",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description89/100
Reverse lookup: every stock where an investor is named in that stock's latest quarter on file, ranked by % held. Each row carries its own quarter_end, so a stock whose newest disclosure is older is visible. An investor that exited, or fell below 1% on the public side, is not returned for that stock. Paged: pass `meta.next_cursor` as `cursor` until `has_more` is false. Use search_investors to find an investor_id.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
investor_id
REQUIRED. investor_id from search_investors or get_named_holders.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Rows per page (default 50, max 200).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
cursor
Opaque paging cursor from meta.next_cursor.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
investor_type
Filter to one investor type, e.g. mutual_fund, insurance, fpi.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
side
promoter | public | all (default all).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
min_pct
Only positions of at least this % of the company.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_investor_holdings",
"title": "Investor Holdings",
"description": "Reverse lookup: every stock where an investor is named in that stock's latest quarter on file, ranked by % held. Each row carries its own quarter_end, so a stock whose newest disclosure is older is visible. An investor that exited, or fell below 1% on the public side, is not returned for that stock. Paged: pass `meta.next_cursor` as `cursor` until `has_more` is false. Use search_investors to find an investor_id.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"side": {
"enum": [
"promoter",
"public",
"all"
],
"type": "string",
"description": "promoter | public | all (default all)."
},
"limit": {
"type": "integer",
"maximum": 200,
"minimum": 1,
"description": "Rows per page (default 50, max 200)."
},
"cursor": {
"type": "string",
"maxLength": 200,
"description": "Opaque paging cursor from meta.next_cursor."
},
"min_pct": {
"type": "number",
"maximum": 100,
"minimum": 0,
"description": "Only positions of at least this % of the company."
},
"investor_id": {
"type": "string",
"description": "REQUIRED. investor_id from search_investors or get_named_holders."
},
"investor_type": {
"enum": [
"promoter",
"mutual_fund",
"insurance",
"pension_fund",
"fpi",
"aif",
"venture_capital",
"sovereign_wealth_fund",
"bank",
"nbfc",
"other_financial_institution",
"government",
"iepf",
"fdi",
"nri_foreign_individual",
"corporate",
"individual",
"unclaimed_suspense",
"other"
],
"type": "string",
"description": "Filter to one investor type, e.g. mutual_fund, insurance, fpi."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Investor Holdings",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Find investors by name prefix (at least 3 characters), among investors currently named in at least one stock, ranked by number of stocks held. Returns investor_id for get_investor_holdings. Names are reported exactly as disclosed, so related entities (a fund house vs its individual schemes) are separate ids.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
q
REQUIRED. Name prefix, e.g. "life insurance".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
query
Alias for `q`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Max results (default 10, max 50).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_investors",
"title": "Search Investors",
"description": "Find investors by name prefix (at least 3 characters), among investors currently named in at least one stock, ranked by number of stocks held. Returns investor_id for get_investor_holdings. Names are reported exactly as disclosed, so related entities (a fund house vs its individual schemes) are separate ids.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"q": {
"type": "string",
"description": "REQUIRED. Name prefix, e.g. \"life insurance\"."
},
"limit": {
"type": "integer",
"maximum": 50,
"minimum": 1,
"description": "Max results (default 10, max 50)."
},
"query": {
"type": "string",
"description": "Alias for `q`."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Search Investors",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description89/100
Returns the complete guide to this server — all tools organised by category, the SEBI disclaimer requirement, and usage patterns for common research tasks.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "read_me",
"title": "Tapetide MCP Guide",
"description": "Returns the complete guide to this server — all tools organised by category, the SEBI disclaimer requirement, and usage patterns for common research tasks.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"title": "Tapetide MCP Guide",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
Shorten the title to an action and subject; move usage details into the description.
Description69/100
Alias for get_stock_quote (same fields, incl. price_basis and last_trade_date). NSE prices can lag the exchange by up to ~15 minutes. Example: {"symbol":"RELIANCE"}.
Describe the returned information so the agent knows whether it will answer the request.
Inputs44/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
REQUIRED. The stock symbol, e.g. "RELIANCE" or "TCS".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ticker
Alias for `symbol`.
Explain the meaning of this value, not just its name.
identifier
Alias for `symbol`.
Explain the meaning of this value, not just its name.
symbols
Alias for `symbol`: exactly one.
Resolve the mismatch between this description and its schema constraints.
Align the title with the capability actually described by this tool.
Description71/100
Not a standalone tool. For ready-made movers use get_trending_stocks; for custom fundamental screens use screen_stocks; for technical screens use screen_stocks_technical.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
Explain the meaning of this value, not just its name.
preset
Ignored — see the redirect message.
Explain the meaning of this value, not just its name.
Annotations100/100
All four behavior hints are declared.
{
"title": "Find the right screening tool",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "run_preset_screen",
"title": "Find the right screening tool",
"description": "Not a standalone tool. For ready-made movers use get_trending_stocks; for custom fundamental screens use screen_stocks; for technical screens use screen_stocks_technical.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"preset": {
"type": "string",
"description": "Ignored — see the redirect message."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Find the right screening tool",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Get the authenticated user's current stock portfolio with live prices. Returns each holding's symbol, company name, quantity, average buy price, current market price, P&L (absolute + %), invested value, portfolio weight %, sector, industry, market cap, PE ratio, dividend yield, and company classification (large/mid/small cap), plus portfolio-level totals.
Returns an empty list when the user has not added any holdings. Holdings can be added with add_portfolio_stocks, including from a pasted broker CSV export.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_user_portfolio",
"title": "User Portfolio Holdings",
"description": "Get the authenticated user's current stock portfolio with live prices. Returns each holding's symbol, company name, quantity, average buy price, current market price, P&L (absolute + %), invested value, portfolio weight %, sector, industry, market cap, PE ratio, dividend yield, and company classification (large/mid/small cap), plus portfolio-level totals.\n\nReturns an empty list when the user has not added any holdings. Holdings can be added with add_portfolio_stocks, including from a pasted broker CSV export.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"title": "User Portfolio Holdings",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
Add one or more stocks to the user's portfolio, merging duplicates by weighted-average price. Accepts a single add, a bulk list, or holdings the user pasted from a broker CSV/table (parse it into the holdings array yourself). Example: "Add RELIANCE 10 shares at ₹1,350" → holdings:[{symbol:"RELIANCE",quantity:10,avg_price:1350}]. STRIP exchange suffixes before calling — -EQ, -BE, -SM, -ST, -BZ, -BL, -RE, -IV, -RR, .NS, .BO — and pass plain NSE symbols (APS-SM → APS; SME stocks are supported). When the user has stated symbol, quantity and price, add them directly. When you PARSED or inferred the holdings (broker CSV, a pasted table, a screenshot), show the parsed rows for confirmation first, and ask rather than guess a missing or ambiguous field. Use search_stocks if a symbol does not resolve. Call read_me for the full broker-CSV procedure.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
holdings › items › symbol
Stock symbol (e.g. RELIANCE, TCS, HDFCBANK)
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
holdings › items › quantity
Number of shares
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "add_portfolio_stocks",
"title": "Add Stocks to Portfolio",
"description": "Add one or more stocks to the user's portfolio, merging duplicates by weighted-average price. Accepts a single add, a bulk list, or holdings the user pasted from a broker CSV/table (parse it into the holdings array yourself). Example: \"Add RELIANCE 10 shares at ₹1,350\" → holdings:[{symbol:\"RELIANCE\",quantity:10,avg_price:1350}]. STRIP exchange suffixes before calling — -EQ, -BE, -SM, -ST, -BZ, -BL, -RE, -IV, -RR, .NS, .BO — and pass plain NSE symbols (APS-SM → APS; SME stocks are supported). When the user has stated symbol, quantity and price, add them directly. When you PARSED or inferred the holdings (broker CSV, a pasted table, a screenshot), show the parsed rows for confirmation first, and ask rather than guess a missing or ambiguous field. Use search_stocks if a symbol does not resolve. Call read_me for the full broker-CSV procedure.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"holdings"
],
"properties": {
"holdings": {
"type": "array",
"items": {
"type": "object",
"required": [
"symbol",
"quantity",
"avg_price"
],
"properties": {
"symbol": {
"type": "string",
"description": "Stock symbol (e.g. RELIANCE, TCS, HDFCBANK)"
},
"quantity": {
"type": "number",
"description": "Number of shares",
"exclusiveMinimum": 0
},
"avg_price": {
"type": "number",
"description": "Average buy price per share in ₹",
"exclusiveMinimum": 0
}
},
"additionalProperties": false
},
"maxItems": 100,
"minItems": 1,
"description": "Array of stocks to add (1-100 items)"
}
},
"additionalProperties": false
},
"annotations": {
"title": "Add Stocks to Portfolio",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description87/100
Update the quantity and/or average price of an existing stock in the user's portfolio.
Use cases:
• User says "I bought 10 more RELIANCE at ₹1,400" → you must calculate the new total qty and weighted avg price, then call this tool
• User says "Change my TCS quantity to 50" → direct update
• User says "I sold 5 shares of INFY" → reduce quantity (calculate new qty = old - 5)
IMPORTANT workflow for additional purchases:
1. First call get_user_portfolio to get current quantity and avg_price
2. Calculate: new_qty = old_qty + additional_qty
3. Calculate: new_avg = (old_qty × old_avg + additional_qty × purchase_price) / new_qty
4. Call this tool with the NEW total quantity and NEW weighted average price
For partial sells:
1. new_qty = old_qty - sold_qty (avg_price stays the same)
2. If new_qty = 0, use remove_portfolio_stocks instead
Both quantity and avg_price are required — always provide the final values.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbol
Stock symbol to update (e.g. RELIANCE)
Clear enough to supply this argument.
quantity
New TOTAL quantity (not the additional amount)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_portfolio_stock",
"title": "Update Portfolio Stock",
"description": "Update the quantity and/or average price of an existing stock in the user's portfolio.\n\nUse cases:\n• User says \"I bought 10 more RELIANCE at ₹1,400\" → you must calculate the new total qty and weighted avg price, then call this tool\n• User says \"Change my TCS quantity to 50\" → direct update\n• User says \"I sold 5 shares of INFY\" → reduce quantity (calculate new qty = old - 5)\n\nIMPORTANT workflow for additional purchases:\n1. First call get_user_portfolio to get current quantity and avg_price\n2. Calculate: new_qty = old_qty + additional_qty\n3. Calculate: new_avg = (old_qty × old_avg + additional_qty × purchase_price) / new_qty\n4. Call this tool with the NEW total quantity and NEW weighted average price\n\nFor partial sells:\n1. new_qty = old_qty - sold_qty (avg_price stays the same)\n2. If new_qty = 0, use remove_portfolio_stocks instead\n\nBoth quantity and avg_price are required — always provide the final values.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"symbol",
"quantity",
"avg_price"
],
"properties": {
"symbol": {
"type": "string",
"description": "Stock symbol to update (e.g. RELIANCE)"
},
"quantity": {
"type": "number",
"description": "New TOTAL quantity (not the additional amount)",
"exclusiveMinimum": 0
},
"avg_price": {
"type": "number",
"description": "New average buy price per share in ₹",
"exclusiveMinimum": 0
}
},
"additionalProperties": false
},
"annotations": {
"title": "Update Portfolio Stock",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Remove one or more stocks from the user's portfolio entirely.
Use cases:
• User says "Remove INFY from my portfolio" → single delete
• User says "Remove all IT stocks" → you identify the symbols from get_user_portfolio, then delete them
• User says "Clear my portfolio" → remove all symbols
IMPORTANT: Always confirm with the user before removing stocks. This action cannot be undone.
For partial sells (reducing quantity), use update_portfolio_stock instead.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbols
Array of stock symbols to remove (e.g. ['INFY', 'TCS'])
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "remove_portfolio_stocks",
"title": "Remove Stocks from Portfolio",
"description": "Remove one or more stocks from the user's portfolio entirely.\n\nUse cases:\n• User says \"Remove INFY from my portfolio\" → single delete\n• User says \"Remove all IT stocks\" → you identify the symbols from get_user_portfolio, then delete them\n• User says \"Clear my portfolio\" → remove all symbols\n\nIMPORTANT: Always confirm with the user before removing stocks. This action cannot be undone.\nFor partial sells (reducing quantity), use update_portfolio_stock instead.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"symbols"
],
"properties": {
"symbols": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 200,
"minItems": 1,
"description": "Array of stock symbols to remove (e.g. ['INFY', 'TCS'])"
}
},
"additionalProperties": false
},
"annotations": {
"title": "Remove Stocks from Portfolio",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description99/100
Get the user's stock watchlist — the stocks they are following, newest first. Returns symbol, company name, sector, industry and the live quote (price, change, change %, previous close; null when unpriced) for each stock, plus a gainers/losers/unchanged tally of the whole list in `movers`. Paged: up to 50 stocks per call; when `has_more` is true, call again with `offset: next_offset` to get the rest (do this before acting on "all" of a long watchlist).
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
offset
Start position for paging (default 0). Pass `next_offset` from the previous page.
Clear enough to supply this argument.
limit
Stocks per page (default and max 50; larger values are clamped).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_watchlist",
"title": "User Watchlist",
"description": "Get the user's stock watchlist — the stocks they are following, newest first. Returns symbol, company name, sector, industry and the live quote (price, change, change %, previous close; null when unpriced) for each stock, plus a gainers/losers/unchanged tally of the whole list in `movers`. Paged: up to 50 stocks per call; when `has_more` is true, call again with `offset: next_offset` to get the rest (do this before acting on \"all\" of a long watchlist).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "number",
"description": "Stocks per page (default and max 50; larger values are clamped)."
},
"offset": {
"type": "number",
"description": "Start position for paging (default 0). Pass `next_offset` from the previous page."
}
},
"additionalProperties": false
},
"annotations": {
"title": "User Watchlist",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Add one or more stocks to the user's watchlist. Idempotent — adding a stock that's already followed is a no-op.
Use cases:
• User says "Watch RELIANCE" → single add
• User says "Add all Nifty IT stocks to my watchlist" → you look up the symbols, then add them
• User says "Track TCS, INFY, WIPRO" → bulk add
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbols
Stock symbols to add to watchlist (e.g. ['RELIANCE', 'TCS'])
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "add_to_watchlist",
"title": "Add Stocks to Watchlist",
"description": "Add one or more stocks to the user's watchlist. Idempotent — adding a stock that's already followed is a no-op.\n\nUse cases:\n• User says \"Watch RELIANCE\" → single add\n• User says \"Add all Nifty IT stocks to my watchlist\" → you look up the symbols, then add them\n• User says \"Track TCS, INFY, WIPRO\" → bulk add",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"symbols"
],
"properties": {
"symbols": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 100,
"minItems": 1,
"description": "Stock symbols to add to watchlist (e.g. ['RELIANCE', 'TCS'])"
}
},
"additionalProperties": false
},
"annotations": {
"title": "Add Stocks to Watchlist",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description78/100
Remove one or more stocks from the user's watchlist.
Use cases:
• User says "Stop watching INFY" → single remove
• User says "Clear my watchlist" → remove all (get watchlist first, paging with next_offset until has_more is false, then remove all symbols)
Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
symbols
Stock symbols to remove from watchlist (e.g. ['INFY', 'TCS'])
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
tapetide setup, tools, quality score, publishing readiness, and alternatives.
How do I add tapetide to Claude, ChatGPT, or Cursor?
Add tapetide to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://mcp.tapetide.com/mcp.
Is tapetide MCP ready for ChatGPT and Claude?
As of November 21, 2026, tapetide scores 91/100 on Manufact's MCP publishing checklist. The scan does not yet meet ChatGPT publishing checks and meets Claude publishing checks. Passing these checks does not guarantee marketplace approval.
How clear is tapetide's MCP tool documentation?
As of November 21, 2026, tapetide scores 79/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 68 of 68 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.
What are the best alternatives to tapetide?
As of November 21, 2026, alternatives to tapetide in financial-services on the Manufact MCP leaderboard include Blockworks, paidfor: x402 seller reliability, SHVL credit control, BankConv, and Economico.
How can tapetide improve its MCP documentation?
get_live_quote is the lowest-scoring reviewed tool at 60/100. No output schema is declared. Add one for structured results so clients can interpret returned fields. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.
Not your MCP?
Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.