Skip to main content
Glama

Recent corporate announcements

recent_alerts
Read-onlyIdempotent

Recent NSE/BSE corporate filings with MarketPing's AI classification — subject, category, document type, importance and sentiment. This is MarketPing's core dataset: use it for 'what has X announced lately', 'any news on X', or (with no company) 'what is happening in the market today'. The classification is MarketPing's reading; to read a filing ITSELF, call fetch with id 'alert:' — it returns the filing's own text, and for a results statement the company's filed figures. Each filing also carries source_url, the original document as filed on BSE or NSE (null when it has none), to cite. Factual data only — MarketPing publishes no buy/sell recommendations, no price targets and no IPO grey-market premium.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recent_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days (default 30, max 365)
companyNoOptional — omit for market-wide announcements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, but the description adds real substance beyond them: the classification is MarketPing's own reading rather than the filing's text, `source_url` may be null, and the dataset is factual only with no recommendations, price targets or grey-market premium. These are behavioral and provenance caveats an agent cannot get from structured fields.

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?

Every sentence earns its place: payload fields first, then when-to-use, then the `fetch` handoff, then citation behavior, then the factual-only disclaimer. It is dense but front-loaded and free of filler.

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 no output schema, the description must carry the return shape and it does — naming the classification fields, the source_url caveat and the id convention needed to chain into `fetch`. For a two-parameter, no-required-input, read-only tool this is 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 `days` (default 30, max 365) and optional `company` are already fully documented in the schema. The description only echoes the omit-company-for-market-wide case, adding no new semantics such as company-name resolution format or interplay between `days` and `company`.

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?

The description states a specific verb+resource — recent NSE/BSE corporate filings with AI classification — and enumerates exactly what each record carries (subject, category, document type, importance, sentiment, source_url). It also explicitly distinguishes itself from the sibling `fetch`, which returns the filing text itself rather than the classified summary.

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

Usage Guidelines5/5

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

Concrete invocation contexts are given as natural queries ('what has X announced lately', 'any news on X') plus the no-company case for market-wide announcements. The exclusion/alternative is explicit: to read the filing itself, call `fetch` with id 'alert:<id>'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.