Skip to main content
Glama
Sign In
India Market MCP

India Market MCP

by kcodweb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Company announcements

get_announcements
Read-onlyIdempotent

Retrieve NSE corporate announcements for a stock symbol—results, board meetings, acquisitions, credit ratings—with summaries, PDF links, and keyword or date filters.

Instructions

Exchange filings from NSE (results, board meetings, acquisitions, credit ratings, investor meets...) with a short summary and a link to each PDF.

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_announcements"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back to look.
limitNoMaximum announcements.
symbolYesNSE symbol, e.g. RELIANCE, TCS, HDFCBANK, M&M.
keywordNoOnly announcements whose category or text contains this, e.g. 'results', 'dividend'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and idempotence are covered. The description adds that each item carries a short summary and a PDF link, which is useful return-format context, but says nothing about the data source's latency, coverage, or failure modes that openWorldHint implies.

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?

A single front-loaded sentence naming the source and resource first, then the return shape. No filler, though the trailing '...' list is slightly loose rather than a precise enumeration.

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

Completeness4/5

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

With no output schema, the description usefully covers what comes back (summary plus PDF link), and the fully-described input schema handles parameter semantics. A note on data freshness or whether results are paginated would make it complete.

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

Parameters3/5

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

Schema description coverage is 100%, so all four parameters (symbol, days, limit, keyword) are already documented in the schema. The description mentions filing categories, loosely mapping to the keyword filter, but adds no new syntax or meaning beyond the schema's own 'e.g. results, dividend' guidance.

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 resource (NSE exchange filings) with a concrete parenthetical list of filing types and the return shape (summary + PDF link). An agent can distinguish it from siblings like get_corporate_actions or get_financials, but it never names or contrasts those siblings explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no pointer to alternatives such as get_corporate_actions for dividends/splits. The scope is inferable from the filings list, but nothing states the condition that should select this tool over a sibling.

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

Deploy Server

Other Tools