Skip to main content
Glama
Prem07a
by Prem07a

historical_valuation

Compare a stock's current P/E against its own historical annual P/E to see if valuation is high or low relative to past. Uses Yahoo Finance data for Indian equities.

Instructions

Compare an NSE/BSE-listed Indian equity's current P/E to its own historical annual P/E (fiscal-year-end price / that year's diluted EPS) over its available history (Yahoo gives ~5 years -- years_used reports the real span, never implies a longer history). Years with negative/missing EPS are excluded. Relative to the company's OWN past only -- not an absolute cheap/expensive judgment or a peer comparison.

:param symbol: ticker symbol, e.g. "RELIANCE", "TCS.NS", or "TCS.BO"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNoEXPENSIVE (>80th percentile), FAIR, or CHEAP (<20th percentile) vs own history
symbolYes
current_peNo
percentileNoCurrent P/E's percentile rank within its own historical annual P/E series
years_usedYesNumber of historical annual P/E data points used
historical_pe_medianNo
currency_mismatch_warningNoSet when Yahoo's market-data and financial-statement currencies disagree for this ticker -- this whole tool (price / EPS) becomes unreliable when set.
Install Server

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are present, but the description compensates with substantive behavioral details: data source (Yahoo, ~5 years), the years_used reporting field, exclusion of negative/missing EPS years, and the relative-to-history framing. This gives the agent a clear picture of what to expect beyond the call itself.

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?

Each sentence adds necessary information: the core operation, data limitations, exclusion rules, and parameter examples. No filler or redundant phrasing, with the main purpose stated first.

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

Completeness5/5

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

For a single-parameter read tool with an output schema, the description covers all necessary invocation details: what it does, how symbols are formatted, what data range to expect, and edge cases. It is complete and self-contained.

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

Parameters5/5

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

The schema has 0% description coverage for the symbol parameter, but the description's ':param symbol:' section provides examples (RELIANCE, TCS.NS, TCS.BO) and implicitly explains exchange suffixes. This fully compensates for the missing schema-level documentation.

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 uses a specific verb ('Compare') and names a precise resource (an Indian equity's current P/E vs its own historical annual P/E). It explicitly distinguishes itself from peer comparisons, making it clearly differentiated from sibling tools like peer_valuation.

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

Usage Guidelines4/5

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

The description clearly states what the tool does and explicitly excludes use cases (absolute cheap/expensive judgments, peer comparison). This gives strong contextual guidance, though it does not explicitly name alternative tools to use for those cases.

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

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/Prem07a/FinMCP'

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