Skip to main content
Glama
screener-mcp
by LogeshR15

get_company_announcements

Read-only

Fetch recent NSE exchange filings for a stock by symbol, filtered by category such as results, dividend, credit rating, or insider trading, and set a lookback window in days.

Instructions

Fetch recent company announcements (exchange filings) from NSE.

symbol: NSE trading symbol (e.g., "TCS", "RELIANCE") category: filter by type — "all" | "results" | "board_meeting" | "dividend" | "insider_trading" | "agm" | "acquisition" | "buyback" | "fund_raise" | "credit_rating" (CRISIL/ICRA/CARE/India Ratings actions — a debt-quality check) | "esg_rating" (ESG scores, which NSE files under "Credit Rating" too) days: how many days to look back (default 30; 730 for the rating categories, since rating actions come once or twice a year; max 3650)

An NSE failure is returned as an error (upstream_unavailable), never as an empty list — an empty list means NSE really has no such filings.

Examples: get_company_announcements("INFY", "results", 90) get_company_announcements("RELIANCE", "credit_rating") get_company_announcements("HDFCBANK", "dividend")

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": {
      "symbol": "<symbol>"
    },
    "name": "get_company_announcements"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
symbolYes
categoryNoall

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds a genuinely non-obvious contract: an upstream NSE failure surfaces as an error (upstream_unavailable) and never as an empty list, so an empty result is trustworthy. It also discloses category-dependent default windows (30 vs 730) and the 3650 cap. It does not cover rate limits or any cap on how many filings are returned, which keeps it off a 5.

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

Conciseness5/5

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

The purpose sentence comes first, then a compact parameter block, then the error-semantics guarantee, then examples — no wasted sentences. The multi-line category enumeration is dense but each entry adds information the schema lacks.

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?

With an output schema present, return values need no explanation, and the description instead covers the things the schema cannot: category vocabulary, lookback strategy, failure semantics, and worked examples. For a three-parameter, zero-coverage schema this is effectively complete.

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

Parameters4/5

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

Schema coverage is 0%, so the description carries the full burden and mostly discharges it: format for symbol, the enumerated category vocabulary plus the meaning of the two ambiguous categories, and the purpose of days with sensible-per-category defaults, reinforced by three examples. The one defect is that it states a days default of 30 while the schema declares default 0, an inconsistency an agent could trip over.

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

Purpose4/5

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

States a specific verb and resource — 'Fetch recent company announcements (exchange filings) from NSE' — and the parenthetical plus the category list scope it tightly enough that an agent can tell it apart from generic news retrieval. It stops short of naming the overlapping sibling (get_insider_trading, which the 'insider_trading' category partly duplicates), so differentiation is inferential rather than explicit.

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?

Gives real selection context inside the tool: which category to pick for which intent ('credit_rating' for a debt-quality check, 'esg_rating' for ESG scores, with the note that NSE files ESG under Credit Rating). It offers no when-to-use-this-vs-another-tool guidance against siblings such as get_recent_news or get_insider_trading, which is the only gap.

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