Skip to main content
Glama

Tapetide - Indian Stock Market MCP

Stock News (alias)

get_stock_news
Read-onlyIdempotent

Alias for get_stock_events with type:"news". Sentiment-tagged news for one stock. Example: {"symbol":"TCS"}.

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": "get_stock_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 20, max 50)
offsetNoRows to skip (default 0); pass meta.next_offset.
symbolNoREQUIRED. The stock symbol, e.g. "RELIANCE" or "TCS".
tickerNoAlias for `symbol`.
identifierNoAlias for `symbol`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip (default 0); pass meta.next_offset.",
      +  "type": "number"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the useful behavioral detail that results are sentiment-tagged and limited to one stock, but says nothing about result size, pagination behavior, or how stale/streamed the news is.

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?

Three short sentences with the alias relationship and subject matter front-loaded, plus a compact example. Nothing is padded, though the quoted type fragment ("type:"news"") is slightly awkward phrasing rather than clean prose.

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?

For a simple single-symbol read tool with full schema coverage, annotations, and no output schema to explain, the description covers identity, scope and result nature adequately. The remaining gap is minor: it does not describe what a news item contains beyond the sentiment label.

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 limit, offset, symbol and its aliases are fully documented in the schema and a baseline of 3 applies. The example {"symbol":"TCS"} illustrates usage but adds no constraint information beyond the schema, and the description does not reconcile the schema's 'REQUIRED' symbol text with the zero required parameters.

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?

The description gives a specific resource ("sentiment-tagged news for one stock") and explicitly frames the tool as an alias for get_stock_events pre-filtered to type "news", which lets an agent separate it from market-wide news (get_market_news) and from the unfiltered sibling. It stops short of a fully self-contained statement of purpose because the actual retrieval semantics must be inferred from get_stock_events.

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

Usage Guidelines3/5

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

Saying it is an alias for get_stock_events with type:news implies the alternative (call get_stock_events with a type filter, or get_market_news for market-wide coverage), but no explicit when-to-use/when-not-to-use guidance or exclusions are stated. The single-symbol scope ("for one stock") is the only implicit constraint.

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.