Skip to main content
Glama
screener-mcp
by LogeshR15

get_recent_news

Read-only

Retrieve recent company news headlines with publisher, UTC publish time, and links, so you can add event context to equity research.

Instructions

Recent news headlines about a company (Google News, Indian edition).

Returns publisher, publish time (UTC) and link for each headline, newest first, de-duplicated. Use it for the "what's happened lately" context that financial statements can't show — results reactions, brokerage calls, management moves, price hikes, regulatory news. For the company's own exchange filings use get_company_announcements instead.

symbol: NSE/BSE symbol or company name days: look-back window (1-90, default 14) limit: max headlines (default 20)

Examples: get_recent_news("TMPV") get_recent_news("Garden Reach", days=30)

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

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo
symbolYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), but the description adds genuine context: newest-first ordering, de-duplication, UTC publish times, and the Indian-edition source. It does not discuss rate limits or empty-result behavior, keeping it short of 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.

Conciseness4/5

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

Front-loads purpose and use cases, then parameter lines, then two examples that each demonstrate a distinct usage (bare ticker vs. free-text name with days). Slightly dense but every sentence carries information.

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?

Output schema handles return shape, annotations handle safety, and the description supplies source, ordering, dedup, parameter bounds, and sibling routing. Complete for a three-parameter read tool.

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 description coverage is 0%, so the description carries the entire burden and does: symbol accepts NSE/BSE ticker or company name, days is a 1-90 look-back window with default 14 (adding a bound the schema lacks), limit defaults to 20. Worked examples disambiguate the string form.

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 (recent news headlines about a company), names the source (Google News, Indian edition), and explicitly distinguishes itself from get_company_announcements for exchange filings. An agent can select 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 Guidelines5/5

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

Gives concrete when-to-use scenarios (results reactions, brokerage calls, management moves, price hikes, regulatory news) and an explicit when-not-to-use routing rule to get_company_announcements. Nothing is left to inference.

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