Skip to main content
Glama
shivamg194-lab

screener-mcp-server

Get Company Overview from Screener.in

screener_get_company_overview
Read-onlyIdempotent

Retrieve a company's key financial ratios (P/E, ROE, etc.), overview description, and pros/cons list from Screener.in for quick snapshot analysis.

Instructions

Fetch a company's snapshot from its Screener.in page: key ratios (Market Cap, Current Price, Stock P/E, Book Value, Dividend Yield, ROCE, ROE, Face Value, etc.), a short "About" description, and Screener's machine-generated Pros/Cons list.

This does NOT include multi-year financial statements — use screener_get_financial_statement for those, or screener_get_peer_comparison for peer benchmarking.

Args:

  • identifier (string): Ticker (e.g. "TCS"), company name (e.g. "Tata Consultancy Services"), or a screener.in company URL/path. If unsure of the exact match, call screener_search_companies first.

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

Returns: JSON: { "name": string, "screenerUrl": string, "aboutText": string|null, "topRatios": [{name, value}], "pros": string[], "cons": string[] }

Examples:

  • Use when: "What's TCS's current P/E and ROE?" -> identifier="TCS"

  • Don't use when: You need 10 years of quarterly revenue (use screener_get_financial_statement instead)

Error Handling:

  • Returns an error if no matching company is found — try screener_search_companies to confirm the right name/ticker first.

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.
Behavior4/5

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

Annotations already declare readOnlyHint=True, idempotentHint=True. Description adds behavioral details like error handling (returns error if no match found), which is useful 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?

Well-structured with sections (description, args, returns, examples, error handling). Every sentence provides value; no 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?

Despite no output schema, description specifies return format as JSON with fields. Covers error handling and prerequisites. Complete for a simple read-only tool.

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 schema already documents both parameters. Description's Args section restates schema info without adding significant new meaning, meeting baseline expectation.

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?

Clearly states the tool fetches a company snapshot including key ratios, about description, pros/cons. Explicitly distinguishes from siblings by listing what it does NOT include (financial statements, peer comparison).

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?

Provides explicit when-to-use (e.g., 'What is TCS's current P/E?') and when-not-to-use (e.g., need multi-year statements, use screener_get_financial_statement). Also suggests using screener_search_companies if unsure of identifier.

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