Skip to main content
Glama
Sign In

DalalOS: Indian Stock Market Research (NSE/BSE)

by in.dalalos
OverviewDiscussionsAdmin

BRSR sustainability disclosures

get_brsr
Read-onlyIdempotent

Use this when the user asks about an Indian company's BRSR (Business Responsibility and Sustainability Report) or ESG disclosures.

Get BRSR (Business Responsibility & Sustainability Report) ESG disclosures for a stock.

Accepts NSE symbol, ISIN, or BSE code. `years` (1..10, default 3) caps fiscal years returned,
newest first. Each year gives curated KPIs grouped as `emissions` (Scope 1/2 + intensity),
`energy`, `water`, `waste`, `social` (female board/KMP %, LTIFR, fatalities, POSH complaints,
CSR spend, ...), `governance`, and `meta` — each `{value, unit}`, raw as filed with SEBI.
`include_raw=True` returns the full ~800-concept BRSR map exactly as disclosed over REST only; MCP omits it (about 150k characters per year).

SEBI's mandatory ESG filing for the top 1000 listed companies (LODR Reg 34(2)(f)). Raw
disclosed figures only — never an ESG score, rating, or verdict (SEBI-RA line). Coverage
starts from whenever the nightly refresh began ingesting the company's BRSR.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "get_brsr"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesOne company: NSE symbol, ISIN or BSE code, e.g. TCS, INE467B01029 or 532540. Always send it as `query` (not `symbol`).
yearsNo
include_rawNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / query / description
      Added value: +"One company: NSE symbol, ISIN or BSE code, e.g. TCS, INE467B01029 or 532540. Always send it as `query` (not `symbol`)."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond them: raw figures as filed with SEBI, no ESG score or rating (SEBI-RA constraint), coverage starting from when nightly ingestion began, and the critical disclosure that include_raw's ~150k-character payload is available over REST only and is omitted on MCP. That last point prevents an agent from expecting data it will never receive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the trigger sentence, then the mechanics, then the return shape and caveats — a sensible order. There is minor redundancy: the BRSR acronym is expanded twice in the first three lines, and the raw-vs-MCP caveat appears twice (once inline, once in the coverage note).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the return-shape burden and does it well: it enumerates the KPI groups (emissions, energy, water, waste, social, governance, meta), states each is `{value, unit}` raw as filed, and explains the raw-map alternative. Combined with the coverage caveat, an agent has everything needed to call it and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% (only `query` is documented), and the description compensates fully: `query` accepts NSE symbol, ISIN, or BSE code; `years` is bounded 1..10, defaults to 3, and returns newest-first; `include_raw` returns the ~800-concept map but is not honored over MCP. This is meaning well beyond the bare integer/boolean schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Get BRSR ... ESG disclosures for a stock") and scopes it to Indian listed companies. No sibling tool in the list covers BRSR or ESG disclosure data, and the description makes that unique domain explicit, so an agent can route to it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit trigger: "Use this when the user asks about an Indian company's BRSR or ESG disclosures." It also implies a boundary by noting SEBI's mandate for the top 1000 listed companies and that coverage begins at nightly-refresh ingestion, which tells the agent when results may be empty. It does not name an alternative tool for ESG-adjacent questions, but none of the siblings overlaps.

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

All DalalOS: Indian Stock Market Research (NSE/BSE) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources