Skip to main content
Glama
screener-mcp
by LogeshR15

get_peer_comparison

Read-only

Compare a company with its sector peers using key Screener.in metrics such as market cap, sales, net profit, PE, and ROCE to assess relative valuation and performance.

Instructions

Get peer comparison table as shown on Screener.in for a company.

Shows the company alongside its sector peers with key metrics like Market Cap, Sales, Net Profit, PE, ROCE, etc.

symbol: NSE/BSE symbol

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_peer_comparison"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
financial_typeNoconsolidated

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-data profile is covered. The description adds useful context about the shape of the result (a peer table with named metrics), but says nothing about failure modes for an unrecognized symbol, dataset freshness, or whether the peer set is fixed by sector or configurable.

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?

Three short lines with the core purpose front-loaded and no filler. The trailing "symbol: NSE/BSE symbol" fragment is useful but reads as an undeclared mini-parameter section rather than a structured part of the description.

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

Completeness3/5

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

An output schema exists, so return-value detail is rightly omitted, and the metric list gives a helpful preview. The main gap is financial_type: with zero schema coverage and no mention in the description, a full parameter of this two-parameter tool is effectively invisible to the agent.

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

Parameters2/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 carry parameter meaning. It partially does for symbol by specifying "NSE/BSE symbol" format, but never mentions financial_type (default "consolidated"), leaving the agent unaware that a standalone-vs-consolidated choice even exists.

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 uses a specific verb+resource ("Get peer comparison table") and enumerates the metrics returned (Market Cap, Sales, Net Profit, PE, ROCE), so the agent knows exactly what comes back. It does not distinguish the tool from the closely named siblings compare_companies or compare_to_sector, which is the only thing keeping it from 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 guidance, no prerequisites, and no exclusions. With three sibling tools (compare_companies, compare_to_sector, get_relative_valuation) covering adjacent territory, the description leaves the agent to guess which one fits, which is a real routing risk.

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