Skip to main content
Glama
shivamg194-lab

screener-mcp-server

Get Peer Comparison from Screener.in

screener_get_peer_comparison
Read-onlyIdempotent

Fetch peer comparison data for a company against its industry peers, showing key metrics such as CMP, P/E, market cap, and ROE.

Instructions

Fetch the peer-comparison table Screener.in shows on a company's page — the same industry peers, compared on CMP, P/E, market cap, ROE, and other columns Screener selects.

Args:

  • identifier (string): Ticker, company name, or screener.in URL/path.

  • consolidated (boolean, default true): Consolidated vs standalone.

Returns: JSON: { "columns": string[], "peers": [{ "name": string, "values": { [column]: string } }] }

Examples:

  • Use when: "How does TCS compare to its industry peers on P/E and ROE?" -> identifier="TCS"

  • Don't use when: You want a custom peer set with your own filter criteria (use screener_run_custom_screen instead)

Error Handling:

  • Returns an error if no peer table is found for the company (uncommon, but can happen for delisted or very niche companies).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYesCompany ticker (e.g. 'TCS', 'INFY'), company name (e.g. 'Tata Consultancy Services'), or a full/relative screener.in company URL/path.
consolidatedNoUse consolidated financials (includes subsidiaries) if true, standalone (parent company only) if false. Default: true.
Behavior5/5

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

Annotations already mark as readOnly and idempotent. The description adds the return JSON structure, error handling for missing peer tables, and confirms it replicates the website's table. No contradictions; adds valuable 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, args, returns, examples, error handling). Every sentence contributes useful information without redundancy or fluff.

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 simple two-parameter tool with no output schema, the description provides a full picture: input types, return format (including structure), usage examples, and an error case. This is sufficient for an AI agent to use correctly.

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% with detailed descriptions for both parameters (identifier and consolidated). The description's Args section merely repeats the schema's information without adding new semantic meaning, so it meets the baseline but doesn't exceed it.

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 fetches the peer-comparison table from Screener.in, specifying it returns industry peers and typical columns. It distinguishes itself from siblings like screener_run_custom_screen by noting this uses Screener's default peer set.

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

Usage Guidelines5/5

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

The 'Examples' section provides explicit use-cases: when to use (comparing a company to peers) and when not to use (custom peer set), even naming the alternative tool (screener_run_custom_screen). This is exemplary guidance.

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/shivamg194-lab/screener-mcp-server'

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