Skip to main content
Glama
pramodhapple504-arch

moneycontrol-mcp

moneycontrol_get_fundamentals

Read-onlyIdempotent

Retrieve valuation ratios, per-share metrics, sector info, and trailing returns for any stock using its symbol and exchange.

Instructions

Get valuation ratios, per-share metrics, sector and trailing returns for a stock.

Covers P/E (standalone & consolidated), industry P/E, P/B, book value, cash EPS, face value, dividend yield, market cap, sector classification, and price returns over 1w / 1m / 3m / 1y / YTD plus 5-year CAGR.

Args: params (FundamentalsInput): - symbol (str): sc_id (preferred) or company name. - exchange (str): 'nse' (default) or 'bse'. - response_format (ResponseFormat): 'markdown' or 'json'.

Returns: str: Fundamentals with this shape (JSON mode): { "name": str, "sc_id": str, "sector": str, "sub_sector": str, "pe": str, "pe_consolidated": str, "industry_pe": str, "pb": str, "book_value": str, "cash_eps": str, "face_value": str, "dividend_yield": str, "market_cap_cr": str, "returns": {"1w": str, "1m": str, "3m": str, "1y": str, "ytd": str, "cagr_5y": str} } Returns "Error: ..." on failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds error behavior ('Returns Error: ... on failure') and a detailed output shape, which provides context beyond annotations.

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 well-structured with clear sections: purpose, coverage, Args, Returns. It is concise without superfluous text, front-loading the main purpose.

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 the presence of annotations, output shape in description, and sibling context, the description is fairly complete. It covers input, output format, error cases, and parameter details. Minor gap: could explicitly contrast with siblings, but not critical.

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?

Although schema description coverage is 0% by metric, the description includes an 'Args' section that explains the purpose of each parameter (symbol, exchange, response_format) and provides default values and constraints, adding meaning beyond the schema.

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 clearly states the tool gets valuation ratios, per-share metrics, sector and trailing returns for a stock. It specifies 'fundamentals' which distinguishes it from sibling tools like moneycontrol_get_history or moneycontrol_get_technicals.

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?

The description implies usage for stock fundamentals but does not explicitly state when to use this tool versus other sibling tools like moneycontrol_get_quote or moneycontrol_get_technicals. No 'when not to use' or alternatives are mentioned.

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

Install Server

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/pramodhapple504-arch/moneycontrol-mcp'

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