Skip to main content
Glama
Sign In
India Market MCP

India Market MCP

by kcodweb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Company financial statements

get_financials
Read-onlyIdempotent

Retrieve annual or quarterly financial statements for NSE-listed companies, with revenue, profit, margins, balance sheet, cash flow and ratios.

Instructions

Reported revenue, EBITDA, operating profit, net profit and EPS with margins and year-on-year growth, plus balance sheet (assets, equity, debt, cash), cash flow (operating, capex, free cash flow) and ROE, debt/equity, current ratio and interest cover. Amounts in ₹ crore.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of periods, newest first.
periodNoAnnual or quarterly results.annual
symbolYesNSE symbol, e.g. RELIANCE, TCS, HDFCBANK, M&M.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent and open-world behavior, so the bar is lower. The description adds genuinely useful operational context the schema lacks: the reporting unit (₹ crore) and the full set of returned metrics, which substitutes for the absent output schema. It says nothing about data coverage, history limits, or behavior when data is unavailable.

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?

A single dense sentence, front-loaded with the primary metrics and ending with the unit convention. Every listed item is meaningful given there is no output schema, though the run-on enumeration is heavy to parse.

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?

With no output schema, the description carries the return-value burden and does so by naming the statements, ratios and currency. It omits any caveat about data availability, history depth, or cases of missing/mixed reporting periods.

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 coverage is 100%, so symbol, period and count are fully documented in the schema itself (including the NSE symbol format and count bounds). The description adds no parameter-level detail beyond the currency unit, so the baseline 3 applies.

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 enumerates exactly which financial data is returned (revenue, EBITDA, balance sheet, cash flow, ratios), so an agent knows this is a fundamentals/statements tool, clearly separable from get_quote or get_price_history. It never explicitly names a sibling to contrast with, so it stops short of a 5.

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 when-to-use statement, no prerequisites, and no routing advice relative to siblings like get_quote or get_shareholding. The usage is only implied by the content listing — an agent must infer that this is for statement-level fundamentals.

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