addrbookFor publishers
← The evidence ledger

Evidence row 577538

Observed , by probe.mcp/1.

Kind
mcp.tools
About
endpoint ece3fee3-4620-4062-bf9b-b72c67dab0bc
Recorded
Previous row
None: the first of its kind about this subject
Body SHA-256
644b1db3f3c8892a944a4d44b6ab11b6d04fa6b2593e358128ec0b3af7571c43
Leaf
0x9e8a1a01965e5176d7df78c72a640766d75917f7cea744b29c9692227641d39b

What was observed

{
  "count": 61,
  "tools": [
    {
      "description": "Use this when the user asks to add, watch or track Indian stocks in their DalalOS watchlist. Changes only the user's own saved list.\n\nAdd one or more stocks to the caller's DalalOS watchlist, accepting a pasted list.\n\n    Use this when the user says \"watch X\", \"track X\", \"add X to my watchlist\", or asks to save\n    stocks they just searched/screened/analyzed via DalalOS for later. This writes to DalalOS's\n    own watchlist, tied to the caller's DalalOS account.\n\n    `symbols` accepts a list of strings or a single string, and any entry may itself be a\n    DELIMITED PASTE -- commas, newlines, semicolons, tabs or pipes -- so a CSV or pasted\n    list of symbols can be handed over as-is. Each fragment is resolved by exact identifier\n    (NSE symbol, ISIN, BSE code) first, then by company name, so \"Gandhar Oil\" becomes\n    GANDHAR. Capped at 200 resolved symbols per call.\n\n    Fragments are never guessed at. The response splits three ways: `watchlist` (added),\n    `unmatched` (no match), and `ambiguous` (two or more plausible matches, returned WITH their\n    candidates so you can ask the user which they meant rather than picking one). Space-separated\n    company names cannot be split reliably -- \"GANDHAR OIL SAVITA OIL\" is one fragment, not two --\n    so ask the user for one per line or comma-separated if a paste comes back unmatched.\n\n    Re-adding a symbol already on the watchlist is a no-op, not an error. Requires an\n    authenticated caller; see `get_watchlist` for the auth error shape.\n    ",
      "inputSchema": {
        "properties": {
          "symbols": {
            "anyOf": [
              {
                "items": {
                  "type": "string"
                },
                "type": "array"
              },
              {
                "type": "string"
              }
            ],
            "title": "Symbols"
          }
        },
        "required": [
          "symbols"
        ],
        "title": "add_to_watchlistArguments",
        "type": "object"
      },
      "name": "add_to_watchlist"
    },
    {
      "description": "Use this when the user asks which Indian companies recently announced a given kind of disclosure, for example order wins or fundraises, across the whole market.\n\nGet every company that filed a matching BSE announcement in a trailing window, market-wide.\n\n    `bucket` is one of the ids from list_announcement_buckets (e.g. \"order-receipts\",\n    \"fundraise\"). `days` (1..90, default 7) bounds the trailing window over filing date. Returns\n    newest first across the WHOLE universe (not one security). Metadata only — the raw disclosed\n    subject/headline plus a link to the source BSE filing; no PDF parsing, no verdicts. Capped\n    at 200 rows; `truncated: true` means more announcements matched the window than were\n    returned (narrow `days` to see the rest) — `total_scanned` reports the true match count,\n    uncapped. Each event carries its `news_id` — pass it to get_filing_extract for that filing's\n    extracted facts.\n    \n\n    When filing prefetch is enabled, an MCP call may enqueue background extraction for\n    eligible listed filings and count accepted jobs against the caller's per-day on-demand cap.\n    The listing response does not wait for extraction.\n    ",
      "inputSchema": {
        "properties": {
          "bucket": {
            "title": "Bucket",
            "type": "string"
          },
          "days": {
            "default": 7,
            "title": "Days",
            "type": "integer"
          }
        },
        "required": [
          "bucket"
        ],
        "title": "get_announcement_bucketArguments",
        "type": "object"
      },
      "name": "get_announcement_bucket"
    },
    {
      "description": "Use this when the user wants end-of-day prices or ratios for several Indian stocks at once (up to 20), for example to line up peers.\n\nGet EOD quotes for up to 20 Indian stocks in one call (peer benchmarking).\n\n    Each item carries the same fields as get_stock_quote (currency, vwap, bse_reported, any\n    valuation_notes/ratios_caveat/dividend fields) plus `status` and `error` keys, so an\n    unresolved or uncached symbol is reported per-item rather than failing the whole batch.\n    ",
      "inputSchema": {
        "properties": {
          "symbols": {
            "items": {
              "type": "string"
            },
            "title": "Symbols",
            "type": "array"
          }
        },
        "required": [
          "symbols"
        ],
        "title": "get_batch_quotesArguments",
        "type": "object"
      },
      "name": "get_batch_quotes"
    },
    {
      "description": "Use this when the user asks about an Indian company's BRSR (Business Responsibility and Sustainability Report) or ESG disclosures.\n\nGet BRSR (Business Responsibility & Sustainability Report) ESG disclosures for a stock.\n\n    Accepts NSE symbol, ISIN, or BSE code. `years` (1..10, default 3) caps fiscal years returned,\n    newest first. Each year gives curated KPIs grouped as `emissions` (Scope 1/2 + intensity),\n    `energy`, `water`, `waste`, `social` (female board/KMP %, LTIFR, fatalities, POSH complaints,\n    CSR spend, ...), `governance`, and `meta` — each `{value, unit}`, raw as filed with SEBI.\n    `include_raw=True` also returns the full ~800-concept BRSR map exactly as disclosed.\n\n    SEBI's mandatory ESG filing for the top 1000 listed companies (LODR Reg 34(2)(f)). Raw\n    disclosed figures only — never an ESG score, rating, or verdict (SEBI-RA line). Coverage\n    starts from whenever the nightly refresh began ingesting the company's BRSR.\n    ",
      "inputSchema": {
        "properties": {
          "include_raw": {
            "default": false,
            "title": "Include Raw",
            "type": "boolean"
          },
          "query": {
            "title": "Query",
            "type": "string"
          },
          "years": {
            "default": 3,
            "title": "Years",
            "type": "integer"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_brsrArguments",
        "type": "object"
      },
      "name": "get_brsr"
    },
    {
      "description": "Use this when the user asks about bulk or block trades in an Indian stock on the NSE.\n\nGet NSE bulk/block trade disclosures for an Indian stock.\n\n    Accepts NSE symbol, ISIN, or BSE code. `deal_type` optionally narrows to \"bulk\" or \"block\"\n    (omitted returns both); `days` (1..1825, default 90) bounds the trailing window; `limit`\n    (1..500, default 100) caps rows returned, newest first.\n\n    Each row is a raw disclosed (symbol, counter-party, direction) record: `client_name`,\n    `buy_sell` (\"BUY\"/\"SELL\"), `quantity`, `price`, and `remarks` (bulk only). NSE's feed reports\n    one row per counter-party + direction, not a matched buyer/seller pair — there is no official\n    \"buyer paired with seller\" record. Only NSE's most-recently-published trading day is fetched\n    upstream (no reachable historical bulk/block archive), so coverage starts from whenever the\n    nightly refresh job began running, not further back.\n    ",
      "inputSchema": {
        "properties": {
          "days": {
            "default": 90,
            "title": "Days",
            "type": "integer"
          },
          "deal_type": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Deal Type"
          },
          "limit": {
            "default": 100,
            "title": "Limit",
            "type": "integer"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_bulk_block_dealsArguments",
        "type": "object"
      },
      "name": "get_bulk_block_deals"
    },
    {
      "description": "Use this when the user asks which macro or commodity factors an Indian company depends on, based on reviewed exposure mappings.\n\nReturn one company's REVIEWED macro-factor exposures, labelled via the factor catalog.\n\n    Cache-only, read-only: the company's reviewed ``company_exposures`` rows joined to the\n    ``factor_registry`` catalog, so each exposure carries its factor label/description/dimension\n    alongside the disclosed pathway (directness/direction/lag/mechanism) and source evidence.\n\n    This is a DIFFERENT tool from ``get_company_macro_exposures`` (two similarly-named tools): this\n    one is the plain, raw per-company evidence listing — no ``as_of_date``/factor filter, no live\n    PPAC/FBIL macro window, no eligibility signals. ``get_company_macro_exposures`` is the\n    signal-eligibility tool that evaluates those exposures against a complete official macro\n    window. Neither ever claims a macro move caused or will cause an earnings/price/investment\n    outcome (SEBI-RA line). A company with no reviewed exposures returns an empty success envelope.\n    ",
      "inputSchema": {
        "properties": {
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_company_exposuresArguments",
        "type": "object"
      },
      "name": "get_company_exposures"
    },
    {
      "description": "Use this when the user asks how an Indian company is exposed to a macro factor such as crude oil, rates or currency, with official context signals.\n\nReturn cached company macro pathway evidence and eligible official context signals.\n\n    Signals are emitted only when an active, reviewed, sourced company exposure passes the\n    factor policy against a complete official PPAC Indian Basket or FBIL USD/INR window. This is\n    conditional context only: it never states that a macro move caused or will cause an earnings,\n    price, or investment outcome. Missing evidence is returned as explicit coverage, not inferred.\n    ",
      "inputSchema": {
        "properties": {
          "as_of_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "As Of Date"
          },
          "factors": {
            "anyOf": [
              {
                "items": {
                  "type": "string"
                },
                "type": "array"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Factors"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_company_macro_exposuresArguments",
        "type": "object"
      },
      "name": "get_company_macro_exposures"
    },
    {
      "description": "Use this when the user asks for an Indian company's disclosed operating figures such as order book, order inflow, capacity or other business KPIs over time.\n\nReturn cached, source-grounded operating KPI history for one company.\n\n    Coverage distinguishes company-disclosed values from ``not_disclosed`` fields. It never\n    infers a current order book from a new order and never fetches or writes on this read path.\n    ",
      "inputSchema": {
        "properties": {
          "from_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "From Date"
          },
          "latest_only": {
            "default": false,
            "title": "Latest Only",
            "type": "boolean"
          },
          "limit": {
            "default": 100,
            "title": "Limit",
            "type": "integer"
          },
          "metrics": {
            "anyOf": [
              {
                "items": {
                  "type": "string"
                },
                "type": "array"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Metrics"
          },
          "query": {
            "title": "Query",
            "type": "string"
          },
          "to_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "To Date"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_company_operating_metricsArguments",
        "type": "object"
      },
      "name": "get_company_operating_metrics"
    },
    {
      "description": "Use this when the user asks what an Indian company listed on NSE or BSE is: its sector, industry, market cap and a headline financial summary.\n\nGet a company profile: identity, sector/industry, market snapshot, and TTM summary.\n\n    Assembled from cached security master + quotes + financials. Accepts NSE symbol, ISIN, or\n    BSE code. `fundamentals` is None when no financials are cached yet; `market` is None when\n    no quote is cached. When present, `market` carries `currency` (\"INR\") and, only when a\n    split/bonus fell inside the trailing 52 weeks, `week52_adjustments` — the same treatment\n    get_stock_quote gives its own snapshot. Both `market` and `fundamentals` may carry caveat\n    fields (e.g. `market.valuation_notes`, `fundamentals.ttm.basis_note`,\n    `fundamentals.latest_period_income.non_recurring_items_note`) when a figure is suppressed\n    or driven by a one-off/non-recurring item — always surface these alongside the figure they\n    annotate rather than the bare number.\n\n    `market.bse_reported`, when present, carries BSE's OWN published ROE/operating margin/net\n    margin — a DIFFERENT, BSE-computed figure (not necessarily the same period or\n    consolidated/standalone basis) from `fundamentals`' XBRL-derived ratios. Cross-check/\n    fallback signal only — never the same number as the computed `roe`/margins.\n    ",
      "inputSchema": {
        "properties": {
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_company_profileArguments",
        "type": "object"
      },
      "name": "get_company_profile"
    },
    {
      "description": "Use this when the user wants a sourced overview of an Indian company listed on NSE or BSE: identity, key facts, recent disclosures and calculations in one report, each linked to its source.\n\nGet a source-linked, read-only canonical company report for one security.\n\n    Accepts an NSE symbol, ISIN, BSE code, or company name. `days` (1-365, default 90) is the\n    reporting window that selects which recent disclosures are in scope. Returns the validated\n    `company_report_v1` model as the envelope `data`: company identity, source-linked `facts`\n    with `citations`, mechanically-computed `calculations`, evidence-referenced `claims`,\n    materiality-bucketed `events`, and a `coverage` block that names any missing reviewed mapping\n    rather than implying non-disclosure.\n\n    This is DalalOS's own consolidated report over its cached exchange filings + reviewed\n    exposure/peer mappings. Read-only: assembled\n    entirely from cache, no upstream fetch and no LLM call. Every number in a claim references\n    the fact/calculation supporting it, and NO verdict, target price, or buy/sell language can\n    appear — the canonical validator rejects such a report before it is ever built (SEBI\n    research-analyst boundary). An unresolvable query (or a required input with nothing cached)\n    returns `reason_code=\"not_found\"`; an out-of-range `days` returns `invalid_argument`.\n    ",
      "inputSchema": {
        "properties": {
          "days": {
            "default": 90,
            "title": "Days",
            "type": "integer"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_company_reportArguments",
        "type": "object"
      },
      "name": "get_company_report"
    },
    {
      "description": "Use this when the user asks about an Indian company's past splits, bonuses, dividends or other corporate actions. For upcoming events across the market use get_market_calendar.\n\nGet the disclosed corporate-action timeline for ONE STOCK, HISTORICAL (splits, bonuses,\n    dividends, etc.) — the per-stock, backward-looking sibling of get_market_calendar (whole-\n    market, any window, all event types merged) and get_upcoming_results (whole-market, forward-\n    only results convenience). Use this tool, not get_market_calendar, when you want one\n    company's corporate-action history rather than a market-wide view.\n\n    Accepts NSE symbol, ISIN, or BSE code. `years` (1..20, default 5) bounds the window.\n    `types` optionally filters to a subset of action types. Newest first; raw disclosures.\n    ",
      "inputSchema": {
        "properties": {
          "query": {
            "title": "Query",
            "type": "string"
          },
          "types": {
            "anyOf": [
              {
                "items": {
                  "type": "string"
                },
                "type": "array"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Types"
          },
          "years": {
            "default": 5,
            "title": "Years",
            "type": "integer"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_corporate_actionsArguments",
        "type": "object"
      },
      "name": "get_corporate_actions"
    },
    {
      "description": "Use this when the user asks how recent DalalOS data is, or when a figure looks stale.\n\nReport cache freshness: last successful refresh per data domain and overall health.\n\n    Every scraper-backed domain (including fii_dii and the ipos family) carries a staleness\n    threshold matched to its real refresh cadence, so a domain whose scraper job silently stops\n    running gets flagged stale rather than reporting `max_age_hours: null` forever.\n    ",
      "inputSchema": {
        "properties": {},
        "title": "get_data_freshnessArguments",
        "type": "object"
      },
      "name": "get_data_freshness"
    },
    {
      "description": "Use this when the user asks how much of an Indian stock's traded volume was taken for delivery, and how that has trended.\n\nGet the delivery-volume / delivery-percentage trend for an Indian stock.\n\n    Accepts NSE symbol, ISIN, or BSE code. `days` (1..1825) bounds the lookback window.\n    Returns the raw delivery quantity and delivery % time series from the NSE bhavcopy.\n    ",
      "inputSchema": {
        "properties": {
          "days": {
            "default": 90,
            "title": "Days",
            "type": "integer"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_delivery_trendsArguments",
        "type": "object"
      },
      "name": "get_delivery_trends"
    },
    {
      "description": "Use this when the user asks about open interest, put-call ratio or futures and options positioning for an Indian stock or an index such as NIFTY or BANKNIFTY.\n\nGet NSE F&O (futures & options) positioning for one underlying.\n\n    Accepts an NSE symbol, ISIN, or BSE code for a stock, OR a raw F&O underlying/index name\n    (e.g. \"NIFTY\", \"BANKNIFTY\") that has no security-master row of its own.\n\n    Returns the latest trading day's aggregate: `futures_oi`/`futures_oi_change`, `call_oi`/\n    `put_oi`, `pcr` (put_oi / call_oi — a mechanically-computed ratio, not a signal),\n    `total_volume`, and `in_ban_list`. Raw NSE bhavcopy figures only — no OI-buildup\n    interpretation or bullish/bearish framing (SEBI-RA line).\n    ",
      "inputSchema": {
        "properties": {
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_derivatives_positioningArguments",
        "type": "object"
      },
      "name": "get_derivatives_positioning"
    },
    {
      "description": "Use this when the user asks whether and when an Indian company paid or declared a dividend, or about its dividend yield.\n\nGet the cash-dividend history for an Indian stock.\n\n    Accepts NSE symbol, ISIN, or BSE code. `years` (1..15, default 5) bounds the window.\n    Returns disclosed dividend amounts per share with ex-dates. Raw disclosures only.\n\n    `annual_totals` (fiscal-year, Apr-Mar buckets) also carries a dividend-YIELD HISTORY: each\n    bucket's `fy_end_price_date`/`fy_end_price` (the closing price on/before that FY's 31 March\n    year-end) and `dividend_yield` (that FY's total dividend / that FY-end close) — None when no\n    price history reaches that far back yet.\n    ",
      "inputSchema": {
        "properties": {
          "query": {
            "title": "Query",
            "type": "string"
          },
          "years": {
            "default": 5,
            "title": "Years",
            "type": "integer"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_dividendsArguments",
        "type": "object"
      },
      "name": "get_dividends"
    },
    {
      "description": "Use this after get_filing_extract when the user wants the earlier state behind an order, capacity or similar event in a filing.\n\nReturn cached prior-state context for a canonicalized filing event.\n\n    Use after get_filing_extract for an order, capacity or other supported event. The result\n    retains source quotes and reports only deterministic historical links; it does not infer\n    price correlation, business causality, or an investment conclusion. Cache-only: no fetches,\n    extraction requests, or writes occur on this tool path.\n\n    ``event_family`` additionally carries the persisted family TIMELINE — every cached filing in\n    this disclosure thread, in filing order — and ``open_questions`` lists the factual follow-ups\n    still unanswered by those filings (e.g. a required contract value the company has not\n    disclosed), each with the filing that raised it and, once answered, the filing that resolved\n    it. Both are raw, source-linked groupings of the company's own disclosures: never a verdict,\n    target, forecast or recommendation.\n    ",
      "inputSchema": {
        "properties": {
          "news_id": {
            "title": "News Id",
            "type": "string"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query",
          "news_id"
        ],
        "title": "get_event_contextArguments",
        "type": "object"
      },
      "name": "get_event_context"
    },
    {
      "description": "Deprecated alias of get_stock_fii_flow; use get_stock_fii_flow for per-stock daily FII transaction flow.\n\nDEPRECATED — renamed to `get_stock_fii_flow`; use that instead.\n\n    Kept as a thin back-compat alias for this release only (no removal date committed yet):\n    delegates to the exact same query function as `get_stock_fii_flow`, so the response is\n    byte-for-byte identical for the same arguments. See `get_stock_fii_flow`'s docstring for the\n    full parameter/behavior description.\n    ",
      "inputSchema": {
        "properties": {
          "days": {
            "default": 90,
            "title": "Days",
            "type": "integer"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_fii_activityArguments",
        "type": "object"
      },
      "name": "get_fii_activity"
    },
    {
      "description": "Use this when the user asks for the contents or a summary of one specific BSE filing of an Indian company, using a news_id from get_stock_events. It may queue processing and use a small daily allowance.\n\nGet the cached PDF-extraction for one BSE corporate filing. Accepts NSE symbol, ISIN,\n    or BSE code + a BSE news_id. Obtain the `news_id` from get_stock_events, which lists a\n    security's recent filings each carrying its `news_id`.\n\n    Returns cached grounded facts + a factual summary extracted from the filing PDF. On a cache\n    miss for any filing that has an attached PDF, calling this tool ENQUEUES on-demand extraction.\n    It waits (up to ~30 seconds) only when the queue estimate says the result can be ready in\n    that time; otherwise it returns at once with `status=\"pending\", queued=true`,\n    `retry_after_seconds` and, when known, an `eta_seconds` estimate from the current queue and\n    recent run times — call again after that long to retrieve the facts. Extraction often takes a\n    few minutes, so to read several filings of one company use get_filing_extracts (up to 10\n    news_ids per call) rather than polling this tool per filing. Extraction works for ANY filing\n    with a PDF, not a fixed doc-type list — EXCEPT financial-results\n    filings, which return `not_queued` reason `results_available_via_financials` (+ a `see_instead`\n    pointer) because their figures come from XBRL via get_financials / get_financial_trends, not\n    PDF extraction. Every `pending` response carries a `reason_code` that stays consistent across\n    repeat polls of the same news_id: `on_demand_processing` (this tool's own trigger enqueued it,\n    or moved an already-queued automatic job up to on-demand priority, and it is still\n    queued/running — keep polling), `auto_backfill_processing` (already being processed by\n    automatic extraction, not this tool — keep polling), or `awaiting_auto_backfill` (not yet\n    queued, but eligible for a future sweep). Other cache-miss statuses: `not_queued` reason\n    `no_document_to_extract` (no PDF), `not_queued` reason `on_demand_quota_exceeded`\n    (authenticated caller hit its per-day on-demand cap — retry tomorrow, or read\n    `attachment_url` directly), or `failed` (retries exhausted; see `error_reason`). Every\n    cache-miss response includes `attachment_url` to read the filing PDF directly. Raw disclosed\n    facts with verbatim source quotes only — no verdicts, targets, or recommendations.\n    ",
      "inputSchema": {
        "properties": {
          "news_id": {
            "title": "News Id",
            "type": "string"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query",
          "news_id"
        ],
        "title": "get_filing_extractArguments",
        "type": "object"
      },
      "name": "get_filing_extract"
    },
    {
      "description": "Use this when the user wants summaries of several filings of one Indian company at once (up to 10 news_ids from get_stock_events). It may queue processing and use allowance.\n\nGet the cached PDF-extractions for several BSE filings of ONE company in one call. Accepts\n    NSE symbol, ISIN, or BSE code + a list of up to 10 BSE news_ids (from get_stock_events).\n\n    Use this instead of calling get_filing_extract once per filing. Each entry in `filings` (in\n    request order) is exactly what get_filing_extract returns for that filing: extracted facts\n    with verbatim source quotes when cached, otherwise `pending` / `not_queued` / `failed` with\n    the same `reason_code` values. Every uncached filing with a PDF is ENQUEUED for on-demand\n    extraction in this one call (each enqueue counts against the caller's per-day on-demand cap;\n    once the cap is reached the rest return `not_queued` reason `on_demand_quota_exceeded`).\n    This tool never waits. When some filings are still `pending`, the response lists them in\n    `pending_news_ids` with one shared `retry_after_seconds`: call this tool again after that\n    long with just `pending_news_ids`. `counts` tallies the entries by status. To keep the\n    response small, a cached filing past the size budget comes back as a stub listed in\n    `omitted_for_size`; fetch it with get_filing_extract (it is cached, so no new extraction). A\n    news_id that is not this company's filing returns `status=\"request_error\"` without failing\n    the batch. Raw disclosed facts with verbatim source quotes only — no verdicts, targets, or\n    recommendations.\n    ",
      "inputSchema": {
        "properties": {
          "news_ids": {
            "items": {
              "type": "string"
            },
            "title": "News Ids",
            "type": "array"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query",
          "news_ids"
        ],
        "title": "get_filing_extractsArguments",
        "type": "object"
      },
      "name": "get_filing_extracts"
    },
    {
      "description": "Use this when the user asks for quarter-on-quarter or year-on-year growth and margin trends of an Indian company period by period.\n\nGet multi-period growth and margin trends for an Indian stock.\n\n    Levels-vs-deltas division: this tool returns a PER-PERIOD time series (QoQ/YoY growth,\n    `net_margin_delta`, `fcf_growth`, and per-period reportable-segment breakdowns, one row\n    per displayed period) — not the latest levels or a summary growth/CAGR block. For the\n    current P&L/balance-sheet levels, TTM, and a single summary `growth` section (annual YoY\n    plus 3y/5y CAGR), see `get_financials` instead.\n\n    Accepts NSE symbol, ISIN, or BSE code. `period_type` is \"quarterly\" (default) or\n    \"annual\"; `limit` (1..12) caps the periods, newest first. Returns level fields plus\n    QoQ/YoY growth and margins — mechanically computed, no verdicts. Each period carries\n    `source` (`\"bse-xbrl\"` post-listing vs `\"drhp\"` pre-listing/prospectus-restated for a\n    newly-listed company); the envelope's own `source` is the shared value or `\"mixed\"`.\n    ",
      "inputSchema": {
        "properties": {
          "limit": {
            "default": 8,
            "title": "Limit",
            "type": "integer"
          },
          "period_type": {
            "default": "quarterly",
            "title": "Period Type",
            "type": "string"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_financial_trendsArguments",
        "type": "object"
      },
      "name": "get_financial_trends"
    },
    {
      "description": "Use this when the user asks how an Indian company listed on NSE or BSE has performed financially: revenue, profit, margins, balance sheet, cash flow or growth, quarterly or annual. Not for non-Indian companies; for a period-by-period growth series use get_financial_trends.\n\nGet consolidated financials (P&L + balance sheet), TTM, and computed margins.\n\n    Accepts an NSE symbol, ISIN, or BSE code. `period_type` is \"quarterly\" (default) or\n    \"annual\". Banks/NBFCs/insurers return an interest-income template (NII / interest\n    income) instead of Revenue / EBITDA. Returns raw line items and mechanically-computed\n    ratios only — no valuation verdicts. Also includes a `growth` section (annual YoY plus\n    3y/5y CAGR for revenue / net income / EBITDA / EPS) — a single summary block layered on\n    top of these levels, NOT a per-period series; for a period-by-period QoQ/YoY growth,\n    margin-delta, and reportable-segment trend series instead, see `get_financial_trends`.\n    The `growth` section here is sign-aware (a loss base/endpoint is\n    Not Meaningful rather than a garbage %), EPS share-adjusted across splits/bonuses, with a\n    `base_effect` flag when a tiny prior-year base inflates the YoY. A `null` inside a present\n    growth metric (as opposed to the metric being absent, which means <2 annual periods are\n    cached) means the growth figure is Not Meaningful for that metric this period — most\n    commonly because the prior-year base (or a CAGR endpoint) was a loss, making a percentage\n    change mathematically undefined or misleading; it is not a data gap. When that is the\n    cause, a sibling `*_not_meaningful_reason` field (e.g. `yoy_not_meaningful_reason:\n    \"prior_period_loss\"`) makes it explicit rather than leaving the `null` to be misread as\n    \"no data available\".\n\n    Also carries three multi-period histories (independent of `period_type`/`limit` — always\n    the full annual history): `interest_coverage_history` (per-year interest-coverage trend,\n    general-only, omitted for banks/NBFCs/insurers or a newly-listed filer), `book_value_history`\n    (per-year book value per share plus a P/B \"band\" against the actual historical price near\n    each period, not general-only), and `working_capital_ratios` (always present: general filers\n    get inventory/receivable/payable days and cash conversion cycle when the latest annual inputs\n    are available; financial institutions receive an explicit not-applicable note).\n\n    Cash flow: each period carries `cash_flow_available` — Indian BSE-XBRL quarterly filings\n    never include a cash-flow statement (only annual filings do), so it is `false` on every\n    period for the default `period_type=\"quarterly\"`; a top-level `cash_flow_note` explains this\n    when no displayed period has cash-flow data. Call with `period_type=\"annual\"` for populated\n    `operating_cash_flow`/`free_cash_flow`/`capex` figures.\n\n    Provenance: each period carries `source` — `\"bse-xbrl\"` for a post-listing exchange filing,\n    or `\"drhp\"` for a newly-listed company's pre-listing years (restated figures from its IPO\n    prospectus, audited per SEBI ICDR requirements). The envelope's own `source` is the shared\n    value, or `\"mixed\"` when a window straddles both; a `drhp_periods_note` explains it further\n    whenever any displayed period is DRHP-sourced.\n    ",
      "inputSchema": {
        "properties": {
          "limit": {
            "default": 8,
            "title": "Limit",
            "type": "integer"
          },
          "period_type": {
            "default": "quarterly",
            "title": "Period Type",
            "type": "string"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_financialsArguments",
        "type": "object"
      },
      "name": "get_financials"
    },
    {
      "description": "Use this when the user asks which Indian stocks are in the NSE futures-and-options ban period today.\n\nGet the full NSE F&O securities-in-ban list for the most-recently-published trading day.\n\n    Market-wide, not per-underlying — no `query` argument. This is the whole-list companion to\n    `get_derivatives_positioning`'s per-symbol `in_ban_list` flag: use this tool when you want\n    everything currently banned in one call, rather than checking symbols one at a time.\n\n    Returns `ban_date` (the snapshot's date) and `symbols` (one entry per banned name, each with\n    `nse_symbol` and `isin` — None for index names, which carry no security-master row). Raw\n    NSE-published ban list verbatim — no \"avoid these\" framing or interpretation (SEBI-RA line).\n    ",
      "inputSchema": {
        "properties": {},
        "title": "get_fno_ban_listArguments",
        "type": "object"
      },
      "name": "get_fno_ban_list"
    },
    {
      "description": "Use this when the user asks how FIIs, DIIs, proprietary traders or clients are positioned in NSE futures and options across the whole market.\n\nGet NSE participant-wise (FII/DII/Pro/Client) F&O open interest & volume — market-wide.\n\n    `days` (1..366, default 30) bounds the trailing window. Each row is one (trade_date,\n    client_type) pair with raw long/short contract counts across futures-index, futures-stock,\n    options-index-call/put, and options-stock-call/put, for both `oi` and `volume`.\n\n    This is a DIFFERENT, derivatives-side signal from `get_market_fii_dii_flow`\n    (market-wide daily CASH-segment net flow) — it is the highest-confidence official\n    substitute for FII/DII derivatives positioning (NSE's cash-market feed does not cover\n    F&O). Raw counts only — no \"smart money\"/positioning-bias interpretation (SEBI-RA line).\n    ",
      "inputSchema": {
        "properties": {
          "days": {
            "default": 30,
            "title": "Days",
            "type": "integer"
          }
        },
        "title": "get_fo_participant_activityArguments",
        "type": "object"
      },
      "name": "get_fo_participant_activity"
    },
    {
      "description": "Use this when the user asks for official FBIL reference rates of the rupee against USD, GBP, EUR, JPY or AED, for example the USD to INR rate.\n\nDaily FBIL INR reference rates (USD/GBP/EUR/JPY/AED/IDR against INR).\n\n    `currency_pair` optionally filters to one pair (e.g. `\"USD/INR\"`, case-insensitive).\n    `from_date`/`to_date` are optional ISO dates (default: trailing 30 days). Each row is\n    `{rate_date, currency_pair, unit_base, rate, source}` — `rate` is always \"INR per\n    `unit_base` units of the foreign currency\" (unit_base is 1 for USD/GBP/EUR/AED, 100 for JPY,\n    10000 for IDR — FBIL's own published denomination, never silently rescaled). FBIL's public\n    feed only serves a rolling ~2-day window with no bulk history archive found, so a fresh\n    deploy accretes this table forward one scheduled refresh at a time — a wide window may\n    legitimately return far fewer rows than the window implies.\n    ",
      "inputSchema": {
        "properties": {
          "currency_pair": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Currency Pair"
          },
          "from_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "From Date"
          },
          "to_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "To Date"
          }
        },
        "title": "get_fx_reference_ratesArguments",
        "type": "object"
      },
      "name": "get_fx_reference_rates"
    },
    {
      "description": "Use this when the user asks for an Indian index's PE, PB or dividend yield over time, for example whether NIFTY 50 is expensive relative to its history.\n\nNSE's own daily OHLC + P/E + P/B + Div Yield time series for one named index.\n\n    `index` is matched case-insensitively against NSE's own published index names (e.g.\n    \"Nifty 50\", \"Nifty Bank\", \"Nifty IT\", \"Nifty Auto\", \"Nifty FMCG\", \"India VIX\" — use\n    get_india_vix for a VIX-specific shape). `from_date`/`to_date` are optional ISO dates\n    (default: trailing ~30 days; window capped at 1825 days). Sourced from NSE's own daily\n    `ind_close_all` file, which carries NSE's ALREADY-COMPUTED P/E, P/B, Div Yield for every\n    index it publishes — sector indices (Nifty Bank, Nifty IT, ...) give an official NSE\n    sector-valuation band, a DIFFERENT figure from get_sector_overview's peer-derived\n    median_pe/median_pb (this project's own aggregate over its tracked universe, grouped by a\n    different taxonomy) — the two are independent, neither validates the other. An unrecognized\n    `index` returns `reason_code: \"no_data\"` with `available_indices_hint` (every index name\n    NSE publishes) — see also list_index_valuations. Raw NSE-published figures only.\n    ",
      "inputSchema": {
        "properties": {
          "from_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "From Date"
          },
          "index": {
            "title": "Index",
            "type": "string"
          },
          "to_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "To Date"
          }
        },
        "required": [
          "index"
        ],
        "title": "get_index_valuationArguments",
        "type": "object"
      },
      "name": "get_index_valuation"
    },
    {
      "description": "Use this when the user asks about the India VIX, the NSE volatility index, today or over a period.\n\nNSE's daily India VIX (volatility index) OHLC time series.\n\n    `from_date`/`to_date` are optional ISO dates (default: trailing ~30 days; window capped at\n    1825 days). Each row is `{trade_date, open, high, low, close, points_change, pct_change}` —\n    VIX has no P/E, P/B, dividend yield, volume, or turnover, so those keys are omitted rather\n    than returned null.\n    ",
      "inputSchema": {
        "properties": {
          "from_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "From Date"
          },
          "to_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "To Date"
          }
        },
        "title": "get_india_vixArguments",
        "type": "object"
      },
      "name": "get_india_vix"
    },
    {
      "description": "Use this when the user asks about Indian IPOs: upcoming, open, awaiting listing or recently listed.\n\nList IPO/public-issue records: upcoming, open, listing pending, or recently listed.\n\n    `status` optionally filters to `upcoming`, `open`, `listing_pending`, or `listed` (omitted returns all four);\n    an unknown value is a bad_request. Unlike most fields, `status` is derived at READ TIME from\n    dates versus today (IST) and a listed-security match. A passed planned listing date without that evidence is `listing_pending`, never `listed`. `limit`\n    (1..500, default 100) caps the result. Each entry carries price band, face value, lot size,\n    issue size, open/close/listing dates, issue price, listing price (once listed), category-wise\n    subscription x-times (QIB/NII/Retail/Employee) where disclosed, a DRHP/prospectus link, and a\n    mechanically-computed `listing_gain_pct` = (listing_price - issue_price) / issue_price\n    (null pre-listing). Sourced from BSE (api.bseindia.com) and SEBI public-issue filings —\n    official sources only. No Grey Market Premium (GMP) field anywhere: GMP has no official\n    exchange source, so it is deliberately excluded (SEBI-RA line — raw facts and mechanical\n    arithmetic only, never a verdict).\n    ",
      "inputSchema": {
        "properties": {
          "limit": {
            "default": 100,
            "title": "Limit",
            "type": "integer"
          },
          "status": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Status"
          }
        },
        "title": "get_iposArguments",
        "type": "object"
      },
      "name": "get_ipos"
    },
    {
      "description": "Use this when the user asks for official Indian macro data: CPI inflation, WPI, IIP, GDP or the crude-oil basket price.\n\nOfficial macro/sector indicators: MOSPI CPI, WPI, IIP (monthly), GDP (annual), and PPAC's\n    Indian Basket crude-oil price (monthly).\n\n    `dataset` is required: `\"cpi\"` (headline Consumer Price Index by sector/division), `\"wpi\"`\n    (headline Wholesale Price Index — overall + food index only), `\"iip\"` (Index of Industrial\n    Production by category), `\"gdp\"` (GDP level + growth rate, current/constant prices, one\n    row per published estimate vintage — First/Second Advance, Provisional, Revised), or\n    `\"crude_basket\"` (PPAC's Indian Basket crude-oil monthly average price, USD/bbl). Any other\n    value is a `bad_request`. `from_period`/`to_period` bound the window (`\"YYYY-MM\"` for\n    cpi/wpi/iip/crude_basket, the fiscal-year string e.g. `\"2024-25\"` for gdp); `series_contains`\n    substring-filters `series_key` (e.g. `\"Food\"`, `\"Manufacturing\"`, `\"GDP Growth Rate\"`; a\n    no-op for crude_basket, which has only one series). `limit` (1..2000, default 200) caps the\n    result, newest period first. Raw published index values/growth percentages/commodity prices\n    only (SEBI-RA line) — no directional commentary (\"inflation is high\", \"oil is expensive\").\n    ",
      "inputSchema": {
        "properties": {
          "dataset": {
            "title": "Dataset",
            "type": "string"
          },
          "from_period": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "From Period"
          },
          "limit": {
            "default": 200,
            "title": "Limit",
            "type": "integer"
          },
          "series_contains": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Series Contains"
          },
          "to_period": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "To Period"
          }
        },
        "required": [
          "dataset"
        ],
        "title": "get_macro_indicatorsArguments",
        "type": "object"
      },
      "name": "get_macro_indicators"
    },
    {
      "description": "Use this when the user asks how many Indian stocks advanced, declined or were unchanged on a trading day.\n\nWhole-market advance/decline/unchanged breadth: how many NSE-listed securities moved\n    up/down/flat on a trading day.\n\n    `from_date`/`to_date` are optional ISO dates (default: trailing ~30 days; window capped at\n    366 days). Each row is `{trade_date, advances, declines, unchanged, total}`, sourced from\n    NSE's own live market-data feed. NSE publishes no bulk historical archive for this figure,\n    so history only extends as far back as this server has been capturing it — an empty result\n    for a genuinely old date is expected, not a bug. Raw counts only — no \"risk-on/risk-off\" or\n    breadth-based market-direction commentary (SEBI-RA line).\n    ",
      "inputSchema": {
        "properties": {
          "from_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "From Date"
          },
          "to_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "To Date"
          }
        },
        "title": "get_market_breadthArguments",
        "type": "object"
      },
      "name": "get_market_breadth"
    },
    {
      "description": "Use this when the user asks what events are scheduled or happened across Indian markets in any date window: results, board meetings, dividends, splits.\n\nGet a unified, WHOLE-MARKET calendar of disclosed events across all NSE/BSE securities,\n    over an ARBITRARY window (past or future).\n\n    Use this instead of get_upcoming_results when you need a past window or multiple event types\n    together; use get_upcoming_results instead when you just want a forward results window with a\n    sector filter (a scoped convenience over the same results data this tool also reads). For ONE\n    company's historical corporate-action timeline, use get_corporate_actions instead — that tool\n    is per-stock; this one is market-wide.\n\n    `date_from`/`date_to` are ISO dates (YYYY-MM-DD); `date_to` must be on or after `date_from`\n    and the window is capped at 180 days. `types` optionally filters to a subset of `results,\n    dividend, split, bonus, demerger, ipo` (plus the remaining corporate-action disclosure\n    types: consolidation, rights, buyback, spinoff, merger, distribution, other) — an unknown\n    type is a bad_request. Each event is `{date, type, isin, nse_symbol, name, detail}`, merged\n    from results_calendar (results) and corporate_action_events (everything else) and sorted\n    chronologically; `limit` (1..2000, default 500) caps the merged result. `ipo` is a stub —\n    no IPO data source exists yet, so it always returns zero rows with an explanatory note.\n    Raw disclosed facts only — no verdicts, no importance ranking beyond your own type filter.\n    ",
      "inputSchema": {
        "properties": {
          "date_from": {
            "title": "Date From",
            "type": "string"
          },
          "date_to": {
            "title": "Date To",
            "type": "string"
          },
          "limit": {
            "default": 500,
            "title": "Limit",
            "type": "integer"
          },
          "types": {
            "anyOf": [
              {
                "items": {
                  "type": "string"
                },
                "type": "array"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Types"
          }
        },
        "required": [
          "date_from",
          "date_to"
        ],
        "title": "get_market_calendarArguments",
        "type": "object"
      },
      "name": "get_market_calendar"
    },
    {
      "description": "Use this when the user asks what FIIs and DIIs have been buying or selling in Indian equities day by day across the whole market. Not for a company's ownership percentage; use get_shareholding.\n\nMarket-wide DAILY FII/DII net cash-flow (Rs crore), NSE cash (Capital Market) segment.\n\n    NOT the shareholding data: get_shareholding gives per-company QUARTERLY FII/DII holding\n    PERCENTAGES; this gives market-wide DAILY net buy/sell/net value in Rs crore -- e.g. \"FIIs\n    net sold Rs 2,340 Cr, DIIs net bought Rs 1,890 Cr\" for a given trading day. `from_date`/\n    `to_date` are optional ISO dates (default: trailing ~30 days); `segment` is \"cash\" only.\n    For NSE participant-wise F&O positioning, use `get_fo_participant_activity`. Raw\n    figures; `net = buy - sell` is the only computation, with no interpretation added.\n    The envelope's `source` reflects actual per-call provenance: recent\n    dates are NSE-live (`source=\"nse\"`), older dates come from a one-time historical backfill by\n    a secondary public source,\n    since NSE publishes no bulk cash-history archive (each row's `source` names its origin), and\n    a query\n    window spanning both returns `source=\"mixed\"`.\n    ",
      "inputSchema": {
        "properties": {
          "from_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "From Date"
          },
          "segment": {
            "default": "cash",
            "title": "Segment",
            "type": "string"
          },
          "to_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "To Date"
          }
        },
        "title": "get_market_fii_dii_flowArguments",
        "type": "object"
      },
      "name": "get_market_fii_dii_flow"
    },
    {
      "description": "Use this when the user wants valuation and returns across the stocks in an Indian index at a glance. Not for ranking by return; use get_top_movers.\n\nGet valuation + multi-horizon returns for the constituents of an Indian market index.\n\n    `index` is matched exactly to a known index name (e.g. NIFTY 50, NIFTY 500) — get the valid\n    names from list_indices. `limit` (1..500) caps the returned constituents, sorted by market\n    cap desc. Each row carries\n    market_cap/pe/pb plus precomputed 1d/1w/1m/3m/6m/1y returns, and any Tier-C\n    structural-event flags on those returns (`return_flags`) or a lack of price history\n    (`incomplete_windows`) — the two are mutually exclusive and together explain every null\n    return. Mechanical facts only — no rankings.\n    ",
      "inputSchema": {
        "properties": {
          "index": {
            "title": "Index",
            "type": "string"
          },
          "limit": {
            "default": 100,
            "title": "Limit",
            "type": "integer"
          }
        },
        "required": [
          "index"
        ],
        "title": "get_market_heatmapArguments",
        "type": "object"
      },
      "name": "get_market_heatmap"
    },
    {
      "description": "Use this when the user compares an Indian company listed on NSE or BSE with similar companies on valuation, margins, returns or debt (PE, PB, debt-to-equity, ROE). For an explainable peer set rather than a table use get_relevant_peers.\n\nCompare a stock against its sector/industry peers on valuation metrics.\n\n    Auto-identifies the peer group and returns a side-by-side table (Mkt Cap, PE, PB,\n    Revenue TTM, net / EBITDA margin, ROE, ROA, ROCE, interest coverage, D/E, the EV bundle\n    — EV, EV/EBITDA, EV/EBIT and the EV-based earnings yield — plus the cash-flow ratios\n    P/CF, P/FCF and FCF yield), sourced entirely from cache. EBITDA-margin and the EV bundle\n    are DELIBERATELY general-only (None for banks/NBFCs/insurers — an intentional validity-\n    matrix decision: EBIT/EBITDA are not meaningful add-backs for a financial's P&L). Cash-flow\n    ratios are NOT gated that way and populate for any peer disclosing an annual cash flow —\n    including banks/NBFCs/insurers. The one exception is bank capex specifically: P/FCF and FCF\n    yield are structurally unavailable for BANK peers whose only cached annual filing predates\n    a capex-mapping fix (banks tag capex under a different XBRL concept than the general\n    template; the mapping now covers it, but existing cached rows need a backfill re-scrape to\n    pick it up) — P/CF (which doesn't need capex) is unaffected either way.\n\n    Each row also carries `piotroski_f_score` (0-9, general-only; None for banks/NBFCs/\n    insurers) and `altman_z_score` (general-only; None for banks/NBFCs/insurers, and for a\n    general filer whenever any of the five classic-formula inputs is undisclosed for that\n    security). The explanatory text for WHY a score is None is never repeated per row — it is\n    deduplicated across the whole peer set and surfaced once at\n    `data.notes.{piotroski_f_score,altman_z_score}` (a list of the distinct reasons actually\n    present in the table). A row with an implausible figure (e.g. a corrupted\n    P/B or a unit-slipped market cap) is marked `valuation_suspect` and excluded from the\n    table-level `peer_medians`; a row within 52 weeks of a rights issue/demerger/merger is\n    marked `ratios_incomplete` (see the table-level `ratios_caveat`), and a row whose margins\n    are dominated by a one-off exceptional/discontinued item is marked `non_recurring_items`\n    (also excluded from `peer_medians`). `grain_widened`/`size_banded` indicate whether the\n    peer set fell back to the broader SEBI industry grain or was restricted by the market-cap\n    size band. Each row also carries `bvps` (book value per share, NOT general-only); the full\n    per-period BVPS + P/B history is get_financials-only.\n    ",
      "inputSchema": {
        "properties": {
          "limit": {
            "default": 8,
            "title": "Limit",
            "type": "integer"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_peer_comparisonArguments",
        "type": "object"
      },
      "name": "get_peer_comparison"
    },
    {
      "description": "Use this when the user asks how much of an Indian company's promoter holding is pledged and how that has changed.\n\nGet the promoter share-pledge percentage trend for an Indian stock.\n\n    Accepts NSE symbol, ISIN, or BSE code. `limit` (1..16) caps the most-recent periods.\n    Returns the reported pledged-percentage time series. Raw disclosures only. Each period\n    carries `pledge_disclosed`: false means this quarter's pledge field wasn't present in the\n    underlying filing (a null `pledged_pct` reads as \"not disclosed\", not \"zero pledge\") — a\n    real 0.0 is only reported when `pledge_disclosed` is true.\n    ",
      "inputSchema": {
        "properties": {
          "limit": {
            "default": 12,
            "title": "Limit",
            "type": "integer"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_pledge_trendArguments",
        "type": "object"
      },
      "name": "get_pledge_trend"
    },
    {
      "description": "Use this when the user wants past share prices of an Indian company listed on NSE or BSE over a period, daily, weekly or monthly, for example to chart or compare a move.\n\nGet the OHLC + volume price-history series for an Indian stock.\n\n    Accepts NSE symbol, ISIN, or BSE code. `days` (1..1825) bounds the lookback window.\n    Set `adjusted=True` for split/bonus-adjusted closes; default is raw close. `interval`\n    is 'daily' (default), 'weekly', or 'monthly' (weekly/monthly resample the adjusted\n    daily series). EOD from the NSE bhavcopy. `currency` is always \"INR\". Each bar carries\n    `sma_50` and `sma_200`, computed from daily split/bonus-adjusted (both modes) closes before resampling, plus a\n    mechanically-computed `vwap` (turnover / volume, None when either is missing/zero); vwap\n    is not rescaled by the split/bonus adjustment factor (turnover/volume are raw flow\n    figures, identical in raw and adjusted mode).\n    ",
      "inputSchema": {
        "properties": {
          "adjusted": {
            "default": false,
            "title": "Adjusted",
            "type": "boolean"
          },
          "days": {
            "default": 90,
            "title": "Days",
            "type": "integer"
          },
          "interval": {
            "default": "daily",
            "title": "Interval",
            "type": "string"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_price_historyArguments",
        "type": "object"
      },
      "name": "get_price_history"
    },
    {
      "description": "Use this when the user asks who an Indian company's real peers or competitors are and why. For a valuation table of peers use get_peer_comparison.\n\nReturn an explainable peer set for operating, financial, or valuation comparison.\n\n    Uses reviewed, provenance-backed business tags and overrides plus cached factual metrics. The\n    existing get_peer_comparison table remains the broader SEBI-classification comparison. This\n    tool may return fewer peers when business-model evidence is insufficient; it never presents a\n    same-industry label as proof of comparability, and returns no investment conclusion.\n    ",
      "inputSchema": {
        "properties": {
          "event_context": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Event Context"
          },
          "limit": {
            "default": 8,
            "title": "Limit",
            "type": "integer"
          },
          "purpose": {
            "default": "operating",
            "title": "Purpose",
            "type": "string"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_relevant_peersArguments",
        "type": "object"
      },
      "name": "get_relevant_peers"
    },
    {
      "description": "Use this when the user asks how much an Indian stock has returned over a period (1 week to max), or about its volatility or drawdown.\n\nGet mechanical return statistics over standard windows for an Indian stock.\n\n    Accepts NSE symbol, ISIN, or BSE code. Returns period returns (1W/1M/3M/6M/1Y/YTD/max),\n    CAGR, annualized volatility, max drawdown, and 52-week high/low — all computed from the\n    split/bonus-adjusted close series. A null return is always explained by exactly one of two\n    fields: `incomplete_windows` (not enough price history for that window yet) or\n    `corporate_action_flagged_windows` (a rights issue/demerger/spin-off/merger/bare\n    consolidation fell inside the window, so the window mixes a mechanical value transfer with\n    ordinary price movement and is nulled rather than reported — see `corporate_action_caveat`\n    when present). If the query only resolved via a rename/merger/demerger-successor alias,\n    the envelope carries `resolved_via` naming which kind fired. Descriptive statistics only;\n    no verdicts.\n    ",
      "inputSchema": {
        "properties": {
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_returnsArguments",
        "type": "object"
      },
      "name": "get_returns"
    },
    {
      "description": "Use this when the user asks about daily FII flow by sector in the historical CDSL data, which stops at March 2025. For current sector flows use get_sector_fpi_investment.\n\nDaily FII/FPI net flow (raw Rs), aggregated by sector -- the sector-wise breakdown.\n\n    Scope-keyed alongside its siblings: get_market_fii_dii_flow is market-wide\n    with no sector dimension; get_stock_fii_flow is per-stock; get_shareholding is per-company\n    QUARTERLY holding %. This is DAILY, per-sector, TRANSACTION flow, joined from the\n    stock-level fii_fpi_stock_flow table against securities.sector (the same sector field\n    get_company_profile/get_sector_overview use). `from_date`/`to_date` are optional ISO dates\n    (default: trailing ~30 days, capped at 366); `sector` optionally narrows to one sector name.\n    `net = buy - sell` is the only computation (SEBI-RA line).\n\n    COVERAGE CAVEAT: sourced from CDSL's Trade-Wise Equity Data of FII/FPI ONLY -- NSDL's\n    per-stock trade data is not ingested, so this is a PARTIAL view of FII/FPI activity by\n    sector, not the whole market's figure (every response carries a `coverage_note` saying so).\n    CDSL stopped publishing after March 2025, so nothing later exists here: for current\n    sector-level FPI flow across both depositories use get_sector_fpi_investment (fortnightly).\n    ",
      "inputSchema": {
        "properties": {
          "from_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "From Date"
          },
          "sector": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Sector"
          },
          "to_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "To Date"
          }
        },
        "title": "get_sector_fii_flowArguments",
        "type": "object"
      },
      "name": "get_sector_fii_flow"
    },
    {
      "description": "Use this when the user asks which Indian sectors foreign portfolio investors are buying or selling, using fortnightly NSDL data.\n\nFortnightly FPI net investment and assets under custody by sector, from NSDL's\n    Fortnightly Sector-wise FPI Investment data. Covers every FPI across BOTH depositories\n    (NSDL and CDSL), 2012 onward -- the current sector-level FPI source; get_sector_fii_flow's\n    CDSL feed stopped publishing after March 2025.\n\n    Scope-keyed alongside its siblings: get_market_fii_dii_flow is market-wide DAILY cash\n    flow; get_sector_fii_flow / get_stock_fii_flow are DAILY CDSL-only transaction flow;\n    get_shareholding is per-company QUARTERLY holding %. This is FORTNIGHTLY, per NSDL sector.\n\n    `from_date`/`to_date` are optional ISO dates matched to each fortnight's period_end\n    (default trailing ~6 months; capped at 5 years unless `sector` is given); `sector` narrows\n    to one NSDL label (case-insensitive; 'Grand Total' is NSDL's all-sector row); `instrument`\n    picks one column (default equity; also debt_general, debt_vrr, debt_far, hybrid, aif,\n    total, mf_equity, mf_debt, mf_hybrid, mf_solution_oriented, mf_other); `include_subsectors`\n    adds pre-2022 nested sub-sector rows, which are already included in their parent. Each row\n    is `{period_start, period_end, taxonomy, sector, row_kind, parent_sector, instrument,\n    net_inr_cr, net_usd_mn, auc_inr_cr, auc_usd_mn}` as NSDL published it (INR crore / USD million;\n    null = not published). Sector labels switch to BSE's Common Industry Classification from\n    2022-04-30 (`taxonomy` marks it) and are NSDL's own, not securities.sector. No computation\n    beyond row selection.\n    ",
      "inputSchema": {
        "properties": {
          "from_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "From Date"
          },
          "include_subsectors": {
            "default": false,
            "title": "Include Subsectors",
            "type": "boolean"
          },
          "instrument": {
            "default": "equity",
            "title": "Instrument",
            "type": "string"
          },
          "sector": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Sector"
          },
          "to_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "To Date"
          }
        },
        "title": "get_sector_fpi_investmentArguments",
        "type": "object"
      },
      "name": "get_sector_fpi_investment"
    },
    {
      "description": "Use this when the user asks how an Indian sector or industry looks in aggregate: number of companies, market cap, valuation and returns.\n\nGet an aggregate market overview by sector (or a finer SEBI grain).\n\n    Omit `sector` to list all groups; pass one to drill in. `grain` is \"sector\" (default),\n    \"igroup\" (SEBI Industry), or \"isubgroup\" (SEBI Basic Industry, the finest grain). Returns\n    count, total market cap, and median/mean PE and median PB per group — computed from\n    cached quotes. Aggregates only.\n    ",
      "inputSchema": {
        "properties": {
          "grain": {
            "default": "sector",
            "title": "Grain",
            "type": "string"
          },
          "sector": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Sector"
          }
        },
        "title": "get_sector_overviewArguments",
        "type": "object"
      },
      "name": "get_sector_overview"
    },
    {
      "description": "Use this when the user asks who owns an Indian company listed on NSE or BSE: promoter, FII, DII, mutual fund and public holding percentages by quarter. Not for daily buying or selling; for daily FII/DII flow use get_market_fii_dii_flow or get_stock_fii_flow.\n\nGet the promoter / FII / DII / public shareholding-pattern time series for a stock.\n\n    Accepts an NSE symbol, ISIN, or BSE code. `limit` caps the most-recent quarterly periods\n    (max 12). Returns raw reported ownership percentages — no verdicts. Sourced from cache;\n    returns an empty series with a note when no shareholding data is cached yet. `breakdown`\n    (when the underlying filing's raw payload was cached) carries the full BSE-SHP\n    institutional sub-category split as `breakdown.institutions`, a list of\n    `{\"category\": ..., \"pct\": ...}` — e.g. Mutual Funds, Insurance Companies, Alternate\n    Investment Funds, Provident/Pension Funds, Sovereign Wealth Funds, Foreign Portfolio\n    Investors Category I / II — separately from the headline `fii_pct`/`dii_pct` aggregates.\n    Category label strings are BSE's own text as filed (may contain formatting artifacts like\n    a trailing \"/\" or doubled spaces), not normalized. Omitted entirely for a period whose raw\n    payload wasn't cached. `breakdown.named_institutional_holders` lists individual FII/FPI,\n    insurance, and mutual-fund holders BSE's filing names once they cross the Reg 31 reporting\n    threshold — `{\"name\": ..., \"category\": ..., \"pct\": ...}` per holder — so a caller can see\n    who specifically holds a stake, not just the category total.\n    ",
      "inputSchema": {
        "properties": {
          "limit": {
            "default": 8,
            "title": "Limit",
            "type": "integer"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_shareholdingArguments",
        "type": "object"
      },
      "name": "get_shareholding"
    },
    {
      "description": "Use this when the user asks what an Indian company has announced or filed on the exchange recently: results, orders, board meetings, fundraising, acquisitions or other disclosures.\n\nGet recent BSE corporate announcements (SEBI Reg-30 disclosures) for an Indian stock.\n\n    Accepts NSE symbol, ISIN, or BSE code. `days` (1..365, default 30) bounds the trailing\n    window over filing date; `category` optionally narrows to one BSE category (e.g.\n    \"Board Meeting\", or \"Insider Trading / SAST\" for promoter/KMP insider buy-sell and pledge\n    creation/invocation/revocation disclosures). Returns disclosure metadata — subject, headline,\n    category, filing time, and a link to the source PDF on BSE. Metadata only; the filings\n    themselves are not parsed or summarised. Quarterly results aren't here — use get_financials\n    for those. Capped at 200 rows; `truncated: true` means more filings matched the window than\n    were returned (narrow `days`/`category` to see the rest) — `total_scanned` reports the true\n    match count, uncapped.\n\n    Each event includes a `news_id` (the BSE filing GUID). To read the extracted facts and a\n    factual summary of a specific filing, pass that `news_id` to get_filing_extract.\n    \n\n    When filing prefetch is enabled, an MCP call may enqueue background extraction for\n    eligible listed filings and count accepted jobs against the caller's per-day on-demand cap.\n    The listing response does not wait for extraction.\n    ",
      "inputSchema": {
        "properties": {
          "category": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Category"
          },
          "days": {
            "default": 30,
            "title": "Days",
            "type": "integer"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_stock_eventsArguments",
        "type": "object"
      },
      "name": "get_stock_events"
    },
    {
      "description": "Use this when the user asks about daily FII transaction flow in one Indian stock in the historical CDSL data, which stops at March 2025.\n\nPer-stock DAILY FII/FPI transaction flow (raw Rs) -- daily series + trailing-30d summary.\n\n    Accepts NSE symbol, ISIN, or BSE code. `days` (1..1825, default 90) bounds the daily\n    `series`; `summary` is always the trailing-30d figure (the SAME single-source helper\n    get_company_profile's compact `fii_activity` field uses). A distinct FII/FPI surface from\n    get_market_fii_dii_flow (market-wide) and get_shareholding (quarterly holding %) -- this is\n    per-STOCK daily transaction flow, aggregated from CDSL's trade-wise disclosure.\n\n    COVERAGE CAVEAT: CDSL-only (NSDL's per-stock data is not ingested), and CDSL stopped\n    publishing after March 2025 -- every response carries a `coverage_note`.\n    `net = buy - sell` is the only computation (SEBI-RA line: no direction calls, no \"smart\n    money\" framing).\n\n    Renamed from `get_fii_activity` so the name carries \"flow\" like its\n    get_sector_fii_flow/get_market_fii_dii_flow siblings (\"activity\" gave no scope cue).\n    `get_fii_activity` is kept as a deprecated back-compat alias for this release.\n    ",
      "inputSchema": {
        "properties": {
          "days": {
            "default": 90,
            "title": "Days",
            "type": "integer"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_stock_fii_flowArguments",
        "type": "object"
      },
      "name": "get_stock_fii_flow"
    },
    {
      "description": "Use this when the user asks for the price, trading volume, 52-week range, PE or PB of an Indian company listed on NSE or BSE. Prices are end-of-day, not live. Not for non-Indian stocks or live intraday prices.\n\nGet the latest end-of-day quote (price, OHLC, volume) for an Indian stock.\n\n    Accepts an NSE symbol, ISIN, or BSE code. Prices are EOD from the NSE bhavcopy. Carries\n    `currency` (\"INR\") and a mechanically-computed `vwap` (turnover / volume for the latest\n    bar, None when either is missing/zero). P/E and P/B may be null with a `valuation_notes`\n    explanation (e.g. negative shareholders' equity, or a proven loss) rather than a\n    misleading ratio. A `ratios_caveat` field and/or a `week52_adjustments` list appear when a\n    split, bonus, or other corporate action in the trailing 52 weeks affects the comparability\n    of the 52-week range or valuation ratios. `recent_dividends` / `upcoming_dividends` /\n    `dividend_yield` carry realized cash-dividend history and trailing yield. Always check\n    these fields before restating a figure as clean.\n\n    A `bse_reported` sub-object, when present, carries BSE's OWN published ROE/operating margin/\n    net margin — a DIFFERENT, BSE-computed figure (not necessarily TTM or the same\n    consolidated/standalone basis) from this project's XBRL-derived ratios elsewhere. It is a\n    cross-check/fallback signal only — never treat it as the same number as a computed `roe`.\n    ",
      "inputSchema": {
        "properties": {
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_stock_quoteArguments",
        "type": "object"
      },
      "name": "get_stock_quote"
    },
    {
      "description": "Use this when the user asks for moving averages, RSI, MACD, Bollinger Bands, beta or circuit-limit data for an Indian stock.\n\nGet moving averages, RSI, MACD, Bollinger Bands, beta, and circuit-filter band/hit-days\n    for an Indian stock.\n\n    Accepts NSE symbol, ISIN, or BSE code. Moving averages (sma_50/sma_100/sma_200), `rsi_14`\n    (Wilder's 14-period RSI), `macd` (12/26/9 EMA line/signal/histogram), `bollinger_bands`\n    (20-day, 2-stdev middle/upper/lower + percent_b), and `beta` (regressed against NSE's own\n    Nifty 50 daily close series over the trailing ~1Y of paired trading days; `beta_benchmark`\n    names it) are all mechanically computed from the split/bonus-adjusted daily close series.\n\n    `circuit_band_pct`/`circuit_band_as_of`/`circuit_hit_days` use the RAW (unadjusted) close\n    series and are NSE's own per-security circuit-filter data, not derived from bhavcopy. NSE\n    publishes only a CURRENT snapshot with no historical archive, so this pipeline's own daily\n    captures are the only source of band history and only exist from whenever this deployment\n    started capturing them:\n    * `circuit_band_pct` is null for TWO DIFFERENT reasons — check `circuit_band_as_of` to tell\n      them apart. `circuit_band_as_of` present + `circuit_band_pct` null means this security\n      genuinely has NSE's \"No Band\" designation (no static daily price band applies — typically\n      a large/liquid, F&O-eligible name; this is a complete, real answer, NOT missing data).\n      `circuit_band_as_of` null means no band has been captured for this security AT ALL yet\n      (also named in `insufficient_history`) — do not conflate the two.\n    * `circuit_hit_days` is a list of `{trade_date, close, prev_close, pct_change, band_pct}`\n      for RAW-close days that plausibly touched that day's captured band (a small tolerance\n      absorbs NSE's tick-size rounding of the actual limit price off the raw percentage) — a\n      descriptive flag that trading was likely constrained that day, not a claim about why.\n    An indicator needing more history than is cached yet (e.g. sma_200 on a recently-listed\n    stock, beta when too few dates overlap the Nifty 50 series, or circuit-band data for a\n    security with no captured band day yet) is null/empty and named in `insufficient_history`\n    rather than computed or fabricated on a short series. Pure math, no verdicts/signals.\n    ",
      "inputSchema": {
        "properties": {
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_technical_indicatorsArguments",
        "type": "object"
      },
      "name": "get_technical_indicators"
    },
    {
      "description": "Use this when the user asks which Indian stocks gained or lost the most, or traded the most, in the last completed session.\n\nRaw ranked gainers/losers/most-active for an index over one completed EOD session.\n\n    `index` defaults to 'NIFTY 500' — get valid names from list_indices. `metric` picks the raw\n    sort field: 'pct_change' (day % change, default), 'change' (absolute price change, Rs),\n    'turnover' (traded value, Rs), or 'volume' (traded quantity). `direction` is 'desc' (default\n    — top gainers / most active) or 'asc' (top losers). `limit` (1..100, default 20) caps the\n    rows. This is the same mechanical fact NSE's own top-gainers/losers page publishes — a\n    caller-chosen sort key over already-public EOD numbers, nothing more.\n    Distinct from get_market_heatmap, which is deliberately NOT sortable by return \n    and instead always sorts by market cap — use get_market_heatmap for a valuation+returns\n    snapshot, use this tool when the question is specifically \"what moved most today\".\n    ",
      "inputSchema": {
        "properties": {
          "direction": {
            "default": "desc",
            "title": "Direction",
            "type": "string"
          },
          "index": {
            "default": "NIFTY 500",
            "title": "Index",
            "type": "string"
          },
          "limit": {
            "default": 20,
            "title": "Limit",
            "type": "integer"
          },
          "metric": {
            "default": "pct_change",
            "title": "Metric",
            "type": "string"
          }
        },
        "title": "get_top_moversArguments",
        "type": "object"
      },
      "name": "get_top_movers"
    },
    {
      "description": "Use this when the user asks which Indian companies report results soon, optionally by sector. For a past window or other event types use get_market_calendar.\n\nList companies with an upcoming board-meeting / results date — WHOLE-MARKET, FORWARD-ONLY.\n\n    This is a forward-only, sector-filterable CONVENIENCE view over the same results_calendar\n    data get_market_calendar also reads — equivalent to get_market_calendar(date_from=today,\n    date_to=today+days, types=[\"results\"]) plus the sector narrowing get_market_calendar doesn't\n    offer, not a competing source. Prefer get_market_calendar instead when you need a past window\n    or multiple event types together. For ONE company's historical corporate-action timeline\n    (splits/bonuses/dividends), use get_corporate_actions instead.\n\n    `days` (1..90, default 14) is the forward window; `sector` optionally filters; `limit`\n    (1..200) caps the results. Each entry carries the meeting date and security identifiers.\n    A disclosed meeting is never dropped just because its bse_code doesn't join cleanly to\n    the securities master; such rows keep the raw bse_code and add a `note` explaining why\n    isin/nse_symbol/name/sector are null.\n    ",
      "inputSchema": {
        "properties": {
          "days": {
            "default": 14,
            "title": "Days",
            "type": "integer"
          },
          "limit": {
            "default": 50,
            "title": "Limit",
            "type": "integer"
          },
          "sector": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Sector"
          }
        },
        "title": "get_upcoming_resultsArguments",
        "type": "object"
      },
      "name": "get_upcoming_results"
    },
    {
      "description": "Use this when the user asks how an Indian stock's PE or price-to-sales ratio has changed over time.\n\nGet point-in-time P/E and price-to-sales history for an Indian stock.\n\n    Each point uses only the TTM filing that was public on that trade date. `days` accepts\n    1..1825; `interval` is daily, weekly, or monthly. P/S is null where the filing lacks a\n    usable top line or disclosed share count. Cache-only, mechanically computed, no verdicts.\n    ",
      "inputSchema": {
        "properties": {
          "days": {
            "default": 365,
            "title": "Days",
            "type": "integer"
          },
          "interval": {
            "default": "daily",
            "title": "Interval",
            "type": "string"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "get_valuation_historyArguments",
        "type": "object"
      },
      "name": "get_valuation_history"
    },
    {
      "description": "Use this when the user asks what is on their DalalOS watchlist, a saved list of stock symbols (not brokerage holdings).\n\nGet the caller's DalalOS watchlist: bare stock symbols, no quantity/cost-basis.\n\n    Use this whenever the user asks what's on their (DalalOS) watchlist, or before adding/\n    removing symbols to check current state. This is DalalOS's own watchlist, tied to the\n    caller's DalalOS account.\n\n    Requires an authenticated caller (API key or OAuth session tied to a DalalOS account) --\n    unauthenticated or auth-disabled deployments get an `unauthorized`/`not_configured` error\n    envelope instead of data. Each entry is decorated with `name`/`sector`/`market_cap` (best\n    effort, via the same lookup `get_company_profile` uses) alongside the bare `symbol` and\n    `added_at`; a symbol that no longer resolves (delisted, renamed) still returns as a bare row\n    rather than failing the whole call.\n    ",
      "inputSchema": {
        "properties": {},
        "title": "get_watchlistArguments",
        "type": "object"
      },
      "name": "get_watchlist"
    },
    {
      "description": "Use this when the user wants to browse market-wide disclosure types, such as order receipts or fundraises, before calling get_announcement_bucket.\n\nList the market-wide BSE announcement discovery buckets (id + label).\n\n    Each bucket groups a real-world disclosure type (e.g. \"order-receipts\", \"fundraise\",\n    \"credit-rating\", \"acquisitions\", \"management-changes\") across the WHOLE market — the inverse\n    of get_stock_events, which is scoped to one company. Pass a bucket id to\n    get_announcement_bucket to fetch its recent filings.\n    ",
      "inputSchema": {
        "properties": {},
        "title": "list_announcement_bucketsArguments",
        "type": "object"
      },
      "name": "list_announcement_buckets"
    },
    {
      "description": "Use this when the user asks which stocks are in an Indian index such as NIFTY 50 or NIFTY Bank.\n\nList the constituent stocks of an Indian market index (e.g. NIFTY 50, NIFTY 500).\n\n    `index` is matched exactly to a known index name — get the valid names from list_indices.\n    `limit` (1..500) caps the returned constituents. Returns the member securities with\n    identifiers (each `nse_symbol`/`isin` can be passed as the `query` to any per-stock tool).\n    ",
      "inputSchema": {
        "properties": {
          "index": {
            "title": "Index",
            "type": "string"
          },
          "limit": {
            "default": 100,
            "title": "Limit",
            "type": "integer"
          }
        },
        "required": [
          "index"
        ],
        "title": "list_index_constituentsArguments",
        "type": "object"
      },
      "name": "list_index_constituents"
    },
    {
      "description": "Use this when the user needs the names of Indian indices that have PE, PB and dividend-yield history.\n\nList every NSE index name tracked (headline, broad-market, sector/thematic, India VIX).\n\n    Each entry carries `{index_name, latest_trade_date, latest_close}`. Powers\n    get_index_valuation's `available_indices_hint` and lets you discover NSE's exact\n    index-name spelling before calling it.\n    ",
      "inputSchema": {
        "properties": {},
        "title": "list_index_valuationsArguments",
        "type": "object"
      },
      "name": "list_index_valuations"
    },
    {
      "description": "Use this when the user needs the list of Indian market indices DalalOS covers.\n\nList the market indices for which constituent membership is cached.",
      "inputSchema": {
        "properties": {},
        "title": "list_indicesArguments",
        "type": "object"
      },
      "name": "list_indices"
    },
    {
      "description": "Use this when the user asks what ready-made screens are available, before calling run_preset_screen.\n\nList the fixed, nightly-precomputed preset screens (name/description/cache freshness).\n\n    Presets are FIXED mechanical filter combinations (never live-queried, never ranked or\n    labelled as a recommendation) — a discovery starting point a caller can further filter via\n    screen_stocks itself. Use run_preset_screen(name) to fetch one preset's actual results.\n    ",
      "inputSchema": {
        "properties": {},
        "title": "list_preset_screensArguments",
        "type": "object"
      },
      "name": "list_preset_screens"
    },
    {
      "description": "Use this only to confirm the DalalOS connection is working.\n\nDalalOS health check. Returns a success envelope to confirm the server is reachable.",
      "inputSchema": {
        "properties": {},
        "title": "pingArguments",
        "type": "object"
      },
      "name": "ping"
    },
    {
      "description": "Use this when the user asks to remove stocks from their DalalOS watchlist. Changes only the user's own saved list.\n\nRemove one or more stock symbols from the caller's DalalOS watchlist in a single call.\n\n    Use this when the user says \"stop watching X\", \"remove X from my watchlist\", or \"clear my\n    watchlist\" (call get_watchlist first, then pass every returned symbol here in one call).\n    This is DalalOS's own watchlist, tied to the caller's DalalOS account.\n\n    `symbols` accepts either a list of strings (mirrors `add_to_watchlist`, capped at\n    200 symbols per call) or a single bare string (kept for one release for\n    backward compatibility with older single-symbol callers). A partial match -- some symbols\n    on the watchlist, some not -- never fails the call: the response reports\n    `{\"removed\": [...], \"not_found\": [...]}` so the caller can see exactly which symbols were\n    actually removed. Requires an authenticated caller; see `get_watchlist` for the auth error\n    shape.\n    ",
      "inputSchema": {
        "properties": {
          "symbols": {
            "anyOf": [
              {
                "items": {
                  "type": "string"
                },
                "type": "array"
              },
              {
                "type": "string"
              }
            ],
            "title": "Symbols"
          }
        },
        "required": [
          "symbols"
        ],
        "title": "remove_from_watchlistArguments",
        "type": "object"
      },
      "name": "remove_from_watchlist"
    },
    {
      "description": "Use this when the user wants the latest result of a named ready-made screen from list_preset_screens.\n\nReturn the last nightly-precomputed result for one registered preset screen.\n\n    `name` must be one of the names returned by list_preset_screens. A preset that has never\n    been computed yet returns an empty result with reason_code \"no_data\". Cache-only — this is\n    the stored output of an equivalent screen_stocks(filters=...) call, not a live query.\n    ",
      "inputSchema": {
        "properties": {
          "name": {
            "title": "Name",
            "type": "string"
          }
        },
        "required": [
          "name"
        ],
        "title": "run_preset_screenArguments",
        "type": "object"
      },
      "name": "run_preset_screen"
    },
    {
      "description": "Use this when the user's screen needs OR logic, arithmetic between two metrics or a screen expression that screen_stocks filters cannot express.\n\nScreen the Indian security universe with one free-form DalalOS screen expression.\n\n    Reach for this instead of screen_stocks when the ask needs OR, arithmetic between two\n    metrics, or a comparison screen_stocks' fixed `<metric>_min`/`_max` keys cannot express — e.g.\n    `Return on capital employed > 22% AND (Debt to equity < 0.5 OR Interest Coverage Ratio > 8)`.\n    screen_stocks stays the right tool for a plain AND-combined set of range filters.\n\n    `dialect` picks the vocabulary and is never guessed: \"screener\" (default) reads common screener\n    ratio names in the units a screener page DISPLAYS — `> 22%` against a ratio stored as a fraction,\n    market cap in crore — while \"dalalos\" reads canonical DalalOS metric ids in the units the\n    cache stores. The metric catalogue for both is GET /v1/ratios; an unrecognised name comes\n    back as an explicit error naming the phrase, never a silent substitution.\n    Query syntax and metric names: https://dalalos.in/docs/screener and\n    https://dalalos.in/docs/screener/ratios.\n\n    Operators: AND, OR, = != > < >= <=, + - * /, and COALESCE, IF, LEAST, POWER, ABS,\n    SQRT, LOG. Missing values follow SQL three-valued logic: a bare comparison against an\n    unknown value does NOT match, `COALESCE(<metric>, 0) > x` does, and `A > x OR B > y` can\n    still match on the right side alone. Division by zero is a missing value, not an error.\n\n    Paging is pinned to one published metrics generation. Each response reports it as\n    `pagination.snapshot_id`; pass that value back as `snapshot_id` on the next page. If a\n    metrics refresh published a new generation in between, the call fails with\n    `snapshot_expired` and the current generation rather than mixing rows from two of them —\n    restart from `offset` 0. `sort_by` is a sortable metric id; ordering puts unknown values\n    last and ends with an ISIN tie-break, so pages never duplicate or skip a row.\n\n    Returns matching securities with the screened metrics — data only, no recommendations.\n    ",
      "inputSchema": {
        "properties": {
          "columns": {
            "anyOf": [
              {
                "items": {
                  "type": "string"
                },
                "type": "array"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Columns"
          },
          "definitions": {
            "anyOf": [
              {
                "items": {
                  "additionalProperties": true,
                  "type": "object"
                },
                "type": "array"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Definitions"
          },
          "dialect": {
            "default": "screener",
            "title": "Dialect",
            "type": "string"
          },
          "limit": {
            "default": 25,
            "title": "Limit",
            "type": "integer"
          },
          "offset": {
            "default": 0,
            "title": "Offset",
            "type": "integer"
          },
          "only_latest_results": {
            "default": false,
            "title": "Only Latest Results",
            "type": "boolean"
          },
          "order": {
            "default": "desc",
            "title": "Order",
            "type": "string"
          },
          "query": {
            "title": "Query",
            "type": "string"
          },
          "scope": {
            "anyOf": [
              {
                "additionalProperties": true,
                "type": "object"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Scope"
          },
          "snapshot_id": {
            "anyOf": [
              {
                "type": "integer"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Snapshot Id"
          },
          "sort_by": {
            "default": "market_cap",
            "title": "Sort By",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "screen_by_queryArguments",
        "type": "object"
      },
      "name": "screen_by_query"
    },
    {
      "description": "Use this when the user asks for Indian stocks matching numeric criteria such as PE, PB, market cap, ROE, margins or debt, optionally within an index such as NIFTY 50. For OR logic or arithmetic between metrics use screen_by_query.\n\nScreen the Indian security universe by user-supplied mechanical criteria.\n\n    All `filters` keys are optional and AND-combined. `sort_by`/`order` order the result set;\n    `limit` (1..100) caps it. Returns matching securities with the screened metrics — data\n    only, no recommendations. An unknown filter key returns a `bad_request` error that lists\n    every accepted key verbatim, so a rejected call is always self-correcting.\n\n    RANGE filters (take a `_min` and/or `_max` suffix, e.g. `pe_min: 10, pe_max: 20`):\n      market_cap, price, pe, pb, deliv_pct, week52_high, week52_low, turnover, num_trades\n      (quote-level) — deliv_pct is a PERCENTAGE (50 = 50%); week52_high/week52_low are rupee\n      price levels comparable to `price`; turnover is a rupee traded-value, num_trades a count.\n      promoter_pct, pledged_pct — PERCENTAGES (pass 50 for \"50%\"), from shareholding data.\n      roe, roa, roce, net_margin, dividend_yield, earnings_yield, fcf_yield, ebitda_margin,\n      operating_margin, quarterly_net_margin_delta_yoy — FRACTIONS (pass 0.15 for \"15%\").\n      interest_coverage, ev, ev_to_ebitda, ev_to_ebit, price_to_cash_flow, price_to_fcf,\n      debt_to_equity, price_to_sales, piotroski_f_score (0-9) — plain multiples/scores, no\n      unit conversion needed.\n      revenue_growth, net_income_growth, quarterly_revenue_growth_yoy,\n      quarterly_net_income_growth_yoy, return_1d/1w/1m/3m/6m/1y — FRACTIONS (0.20 = 20% growth\n      or return); unlike the margin/yield group above, these may legitimately exceed 1.0\n      (>100%) for high-growth or multi-bagger names.\n      pct_off_52w_low — derived, FRACTION: (price - week52_low) / week52_low, e.g.\n      `pct_off_52w_low_max=0.05` for \"within 5% of its 52-week low\".\n      num_shareholders (a count) and promoter/fii/dii/public_holding_change_qoq — PERCENTAGE POINTS between the latest two shareholding filings (50% -> 55% is 5, not 0.10) — plus num_shareholders_change_qoq, a plain count difference. A\n      security with only one filed period is EXCLUDED, never matched as a zero change.\n      revenue_cagr_3y/5y, net_income_cagr_3y/5y — 3Y/5Y sales and profit CAGR, FRACTIONS.\n      roe_weighted_avg_3y/5y, roce_weighted_avg_3y/5y — multi-year return on equity /\n      capital employed, FRACTIONS, computed as sum(numerators)/sum(denominators) over the\n      window (denominator-WEIGHTED, not the average of the yearly ratios). All eight are\n      null unless that many annual periods are cached; the 5Y horizons are null for most\n      names today.\n      sales_growth_ttm, profit_growth_ttm — TTM vs the preceding TTM, FRACTIONS, and like the\n      other growth rates they may legitimately exceed 1.0. roa_last_year — last ANNUAL\n      profit over average assets (roa's trailing-twelve-month sibling), a FRACTION.\n      opm_ex_other_income — operating margin on the Schedule-III Sales-minus-Expenses\n      subtotal, so it EXCLUDES other income, a FRACTION; operating_margin keeps its EBIT\n      basis. roce_ex_exceptional — roce with the pre-tax exceptional item removed, a\n      FRACTION. pe_ex_exceptional — market cap over TTM profit with the after-tax\n      exceptional item removed, a multiple; the headline pe keeps its own basis.\n      price_to_fcf_3y_avg — market cap over 3-year-average free cash flow, a multiple.\n      inventory_days_material_cost, payable_days_material_cost — DAYS, on a material-cost\n      denominator rather than full COGS. working_capital_ex_st_borrowings — RUPEES, with\n      short-term borrowings netted out. Each of these stands BESIDE the DalalOS metric of\n      the same family rather than replacing it, so both bases are screenable.\n\n    EXACT-MATCH filters (single value, no `_min`/`_max`):\n      sector, industry, igroup, isubgroup, company_type (e.g. \"bank\", \"nbfc\", \"insurer\",\n      \"general\"), index (e.g. \"NIFTY 50\" — membership in that index's constituent list).\n\n    BOOLEAN filter (a bare true/false, no `_min`/`_max`):\n      is_sme — listed on an SME platform (NSE Emerge). THREE-VALUED: a security whose listing\n      segment is unverified matches neither is_sme=true nor is_sme=false, because no\n      official machine-readable BSE SME membership list exists.\n\n    Some derived metrics are general-only (null for bank/nbfc/insurer): roce,\n    interest_coverage, ev*, earnings_yield, ebitda_margin, operating_margin,\n    piotroski_f_score, roce_weighted_avg_3y/5y, opm_ex_other_income,\n    roce_ex_exceptional, inventory_days_material_cost, payable_days_material_cost.\n    ",
      "inputSchema": {
        "properties": {
          "filters": {
            "additionalProperties": true,
            "title": "Filters",
            "type": "object"
          },
          "limit": {
            "default": 25,
            "title": "Limit",
            "type": "integer"
          },
          "order": {
            "default": "desc",
            "title": "Order",
            "type": "string"
          },
          "sort_by": {
            "default": "market_cap",
            "title": "Sort By",
            "type": "string"
          }
        },
        "required": [
          "filters"
        ],
        "title": "screen_stocksArguments",
        "type": "object"
      },
      "name": "screen_stocks"
    },
    {
      "description": "Use this when the user needs historical detail from an Indian company's earlier filings, for example a prior order value or commissioning date.\n\nSearch this company's already cached official filings, page by page.\n\n    Use after get_stock_events/get_filing_extract when you need historical context, such as a\n    prior commissioning date, original order announcement, customer, project, or tender. This is\n    cache-only: it never downloads a filing or triggers extraction. Results retain a source page\n    and original BSE attachment URL; `coverage` tells you how much page-preserving history is\n    indexed and explicitly reports parsed legacy filings that cannot be searched reliably yet.\n    ",
      "inputSchema": {
        "properties": {
          "document_types": {
            "anyOf": [
              {
                "items": {
                  "type": "string"
                },
                "type": "array"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "Document Types"
          },
          "from_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "From Date"
          },
          "limit": {
            "default": 10,
            "title": "Limit",
            "type": "integer"
          },
          "query": {
            "title": "Query",
            "type": "string"
          },
          "search_text": {
            "title": "Search Text",
            "type": "string"
          },
          "to_date": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "title": "To Date"
          }
        },
        "required": [
          "query",
          "search_text"
        ],
        "title": "search_company_disclosuresArguments",
        "type": "object"
      },
      "name": "search_company_disclosures"
    },
    {
      "description": "Use this when the user names an Indian company, NSE symbol, BSE code or ISIN and you need to identify the listed security before calling another tool. Not for US or other non-Indian stocks.\n\nFind Indian stocks by company name, NSE symbol, BSE code, or ISIN.\n\n    Returns matching securities with their ISIN, internal company_id, name, and both\n    exchange codes. Use this first when a ticker is unknown or ambiguous, then pass a returned\n    `nse_symbol` / `isin` / BSE code as the `query` argument to any other per-stock tool.\n    Tolerant matching: a company-name/symbol typo still surfaces a suggestion, a truncated/\n    partial ISIN or BSE code matches via prefix, and a former/retired name or symbol (e.g. a\n    pre-rename company name) resolves to the security's current identity, with `resolved_via`\n    on the result naming which kind of resolution fired.\n    ",
      "inputSchema": {
        "properties": {
          "limit": {
            "default": 10,
            "title": "Limit",
            "type": "integer"
          },
          "query": {
            "title": "Query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "title": "search_stocksArguments",
        "type": "object"
      },
      "name": "search_stocks"
    }
  ]
}

What the leaf hashes

{"body":"644b1db3f3c8892a944a4d44b6ab11b6d04fa6b2593e358128ec0b3af7571c43","id":577538,"kind":"mcp.tools","method":"probe.mcp/1","observed_us":1793142635036861,"prev":null,"subject":"ece3fee3-4620-4062-bf9b-b72c67dab0bc","subject_kind":"endpoint"}

Proof

Fold these into the leaf in order, hashing each sorted pair with keccak256, to reach the root of (273461 rows).

  1. 0x9e8a032d2a95b199bbfc538622d0c9d0397de44f726686660f70d210f5ae76b6
  2. 0xa692d07e67763cc4a8d0c033f228670236f3017a3b248d9d47895788f5593573
  3. 0x2c882eb4c3d28a4f69a2c0ab8fc2d0ef4ea83dee133f99cb93396f59d7fe3da1
  4. 0x5b1e8fffa9adc11d84ce4ebba0a9d168a8c90bc17e48e3b854631856d4bef9a5
  5. 0x9ad3de37570378d0f5edf0a9a3e67733d45b62ac4a05597c6d203028f53aa267
  6. 0x62ce8a1f6ab60c9b6dcb3e3f79f38b839120cbf368fbdcea556ebe1f15075da6
  7. 0x9c1320f63f4e8be11eb6423ce834483fe56891bd5da1dc4fed1a78389527f22d
  8. 0xa4d82646592870aa6d96381746d2af33e0d6256791b7b7c5f8d2dc9b1b14de6f
  9. 0x217e8febbf10e5374c252bf5ed797554272a6919be2a757faf8681258be8424c
  10. 0x3661fc103f9e8ae5a55d05dfa93995ef65fee8ded3bc01a5e72ec06886163e17
  11. 0xb1ccf28ab1a7fa316a090ec87291371439da179c523f84e00e64a6628e44fced
  12. 0x121ffc8b387c54931bc53056e106d9ada0e2f7c1d32ebc819c3306406c952295
  13. 0xa91c23113464e2fc1e93d41e407b7c6c254bee2eac2f7a550e2f9a1275eef26a
  14. 0xb37e6165108af3c1962db6b76953aee5ee86201747a07444ad2760bf2d5dca23
  15. 0xa3fff4662cd48659f5bafd0612931759a90e53a7b4209ed8f26f6594a07bb547
  16. 0x64c405a28e8819716221eb2529fe4ce277ab08025e17e685cbd5ece75ceb75c7
  17. 0xf30fddbf4811226c58e8f0daf36fddd79fc5f1356b592bb1d99a8061ddbabe66
  18. 0x2bf8151e5f157dd183b9de6fa00469551932a7a6e3f33a694895000ac9061197
  19. 0x9fc354c0ea3efc3f1b6548bb77ea902a50f2c9647647ea61592efce2bd795699
Day root
0xdd77e5e99da32c3f154180d63e3c3e6fe11e896a2c6896412ef6b5c4bcf7e795
Chained
0x23bb4dfd09f55c15ac3962f53578e02c6114d5bfd9bb451cf8794fb6e2817ef4
Published
On Arc Testnet, block 69414147: 0xb2ebd83aafeb765a0ce66e76aefb133ed06606c98038fd56191e2bcd1dcb77b4

How to check it · This row as JSON