Skip to main content
Glama
screener-mcp
by LogeshR15

get_relative_valuation

Read-only

Compare up to 20 stocks’ P/E and ROCE with their Screener industry medians to identify relative cheapness, premiums, or potential value traps.

Instructions

Is this P/E cheap for its industry? Compares each stock's P/E and ROCE with the median of every listed company in its Screener industry, for up to 20 stocks in one call (stocks in the same industry share one fetch, so this scales across a screen's results).

Returns per stock: industry, P/E vs industry median (%), ROCE vs median (pp), and a one-line assessment (e.g. "at a premium to its industry, but the premium comes with clearly higher ROCE", or a possible value trap). Sorted cheapest-vs-industry first.

symbols: list (["HBLENGINE", "BSE", "TCS"]) or comma-separated string

Tip: screen_stocks(..., peer_relative=True) attaches the same data to screen results directly.

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": {
      "symbols": "<symbols>"
    },
    "name": "get_relative_valuation"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already state readOnlyHint and openWorldHint, so the safety profile is covered. The description adds non-obvious behavior beyond that: stocks in the same industry share one fetch, the 20-stock cap, the sort order (cheapest-vs-industry first), and the nature of the generated assessment including the value-trap case.

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?

Front-loaded with the question the tool answers, then scope, return shape, argument format, and the cross-tool tip — each block earns its place. No filler sentences or restated annotations.

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?

With an output schema and annotations present, the description need not enumerate return fields, yet it summarizes them helpfully, and it covers batching limits, sort order, and the preferred alternative path. Nothing an agent needs to call this correctly is missing.

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?

Schema description coverage is 0% and there is one parameter, so the description must carry the load — and it does, giving both accepted forms (list or comma-separated string) with a concrete example. The one gap is the hard cap of 20 stocks not being repeated as a per-argument constraint for symbols.

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 names a specific comparison (P/E and ROCE vs Screener-industry median) and frames it with a concrete question, so the operation and its unit of analysis are unambiguous. It also states scope (up to 20 stocks, one call) and distinguishes itself from the sibling screen_stocks path via the peer_relative tip.

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?

It gives a clear when-to-use trigger (checking whether a P/E is cheap for its industry) and an explicit batching limit of 20 stocks, plus a tip routing the agent to screen_stocks(..., peer_relative=True) when the data is wanted on screen results. It stops short of naming when NOT to use this, e.g. custom peer sets via get_peer_comparison.

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