Skip to main content
Glama
Prem07a
by Prem07a

get_company_news

Fetch recent news headlines and summaries for NSE/BSE-listed Indian stocks. Use the mentions_company flag to filter relevant coverage from broader industry stories.

Instructions

Get recent news headlines/summaries for an NSE/BSE-listed Indian equity.

Yahoo's news stream for a ticker is loosely sector/theme-tagged, not a
strict per-company filter -- expect some broader industry or
competitor coverage mixed in with company-specific stories, and
occasionally an outright unrelated item. Each article's
`mentions_company` flag is a rough, mechanical relevance signal (does
the company's name/ticker literally appear in the title/summary), not
a guarantee either way -- use it to weigh results, not to assume
everything returned is deeply relevant or that a False is noise.

An empty result is a legitimate outcome (no recent coverage indexed --
common for small/micro caps), not necessarily an error; the ticker is
still validated first, so an invalid symbol raises rather than
silently returning empty.

:param symbol: ticker symbol, e.g. "RELIANCE", "TCS.NS", or "TCS.BO"
:param limit: max number of articles to return (default 10)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
symbolYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoSet when articles is empty: could mean no recent Yahoo-indexed coverage (common for small/micro caps) or an invalid symbol -- confirm the ticker via search_ticker/get_company_profile if unsure
symbolYes
articlesYes
Install Server

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations present, the description fully carries the burden of behavioral disclosure and does so very well. It explicitly warns that Yahoo's news stream is loosely tagged and may contain broader industry/competitor/unrelated items, explains the mechanical `mentions_company` flag, and addresses both empty-success and invalid-symbol failure modes.

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 description is front-loaded with the core purpose and every subsequent sentence earns its place: noise caveat, relevance flag caveat, empty-result semantics, validation note, and parameter docs. All are essential to correct invocation in an agentic context.

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 and only two simple parameters, the description covers all contextual gaps: result-relevance expectations, failure behavior, and parameter syntax. No critical information needed to call or interpret the tool is missing.

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?

Despite 0% schema coverage, the description fully documents both params in the `:param` block: symbol gets ticker examples (RELIANCE, TCS.NS, TCS.BO) and limit's meaning/default are stated. This adds substantial value beyond the bare input schema and gives an agent everything needed to fill the args correctly.

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 opens with a specific verb ('Get recent news headlines/summaries') and explicitly scopes the resource to NSE/BSE-listed Indian equities. This clearly distinguishes it from all sibling tools, which are financial analysis and data lookup operations rather than news retrieval.

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?

The description provides clear context for when the tool is appropriate: any time recent news coverage for an Indian listed equity is needed. It also clarifies edge-case behavior (empty result is legitimate, invalid symbols raise), though it does not name alternatives because none of the siblings offer news.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Prem07a/FinMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server