Skip to main content
Glama
tynorn1

Indian Stock Analysis MCP Server

by tynorn1

stock_quote

Retrieve current stock price and basic trading information for any Indian stock by providing its ticker symbol on BSE/NSE.

Instructions

Get current stock price and basic trading information for Indian stocks.

Args: ticker: Indian stock ticker symbol (e.g., 'RELIANCE', 'TCS', 'INFY')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It does not mention whether the quote is real-time or delayed, which exchange or market hours apply, or how errors or unknown tickers are handled. The word 'current' is unqualified.

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 extremely concise and front-loaded, with no filler. The Args section repeats the schema but earns its place by adding concrete examples and clarifying the Indian-stock scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although an output schema exists and the tool is simple, the description lacks usage guidance and behavioral caveats. An agent still does not know when to prefer this over sibling tools or what limitations apply, leaving meaningful gaps for a tool with no annotations.

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 0%, so the description must compensate. It adds meaning by defining ticker as an 'Indian stock ticker symbol' with examples like RELIANCE, TCS, and INFY. However, it omits format details such as exchange suffix, case sensitivity, or validation rules.

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 a specific verb and resource: 'Get current stock price and basic trading information for Indian stocks.' It distinguishes this quote-focused tool from analysis, forecasting, and fundamentals siblings, though 'basic trading information' is somewhat vague and it does not explicitly name alternatives.

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?

There is no explicit guidance on when to use this tool versus siblings like technical_analysis, company_fundamentals, or forecast_arima_model. The only implied usage is for current price lookups, but no exclusions or alternative routing are provided.

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

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/tynorn1/stock-analysis-mcp'

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