Skip to main content
Glama
Sign In
trading-mcp-server

trading-mcp-server

by mukul8896
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fetch_market_news

Retrieve Indian market news for stocks, filtered by category (e.g., earnings, corporate actions) and sentiment (positive, negative, neutral).

Instructions

Broad Indian-market news feed (Tradient, free).

category: all | companies | <sub_category>, where sub_category is one of earnings-financial-results | corporate-actions | operational-updates | management-leadership | legal-compliance | product-launches-innovation | others. Matched against both category and sub_category. sentiment: all | positive | negative | neutral.

Each item: symbol, stock_name, title, text, sentiment, category, sub_category, sector, publish_date (epoch ms).

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

Input Schema

NameRequiredDescriptionDefault
categoryNoall
sentimentNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries full responsibility. It implies a read-only, non-destructive operation by being a 'feed', but does not explicitly state no side effects, authentication needs, or rate limits. It does list return fields, which adds some transparency.

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 concise and well-structured, with the main purpose in the first sentence followed by clear parameter details and a list of return fields. No unnecessary information.

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?

Given low complexity (2 params, no output schema), the description adequately explains parameters and return fields. It lacks mention of pagination or result limits, but these are not critical for basic usage.

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

Parameters4/5

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

The schema provides no descriptions (0% coverage), so the description adds significant meaning by explaining valid values for category (all, companies, sub_category list) and sentiment (all, positive, negative, neutral), plus how category matching works. However, 'companies' as a category is not elaborated.

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 clearly states it is a 'Broad Indian-market news feed', specifying the resource and action. However, it does not differentiate from sibling tools like fetch_latest_news or fetch_news_articles, which are also news-related.

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?

No guidance is provided on when to use this tool versus other news tools (e.g., analyze_news_sentiment, fetch_latest_news). The description does not mention prerequisites, context, or alternatives.

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