Skip to main content
Glama
shivamg194-lab

screener-mcp-server

Search Companies on Screener.in

screener_search_companies
Read-onlyIdempotent

Search Screener.in for Indian companies by name or ticker symbol, and get the unique ID and URL for subsequent financial analysis.

Instructions

Search Screener.in for listed Indian companies by name or ticker symbol.

Use this first when you're not sure of a company's exact ticker or how Screener.in identifies it — the result's "id" or "url" can be passed as the identifier to the other screener_* tools.

Args:

  • query (string): Company name or ticker, e.g. "TCS", "Infosys", "HDFC Bank"

Returns: JSON with a "results" array, each item having: { "id": string, "name": string, "url": string (relative screener.in path) }

Examples:

  • Use when: "Find the ticker for Tata Consultancy Services" -> query="Tata Consultancy"

  • Don't use when: You already have the exact ticker (just call screener_get_company_overview directly)

Error Handling:

  • Returns an empty "results" array if nothing matches

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesCompany name or ticker symbol to search for, e.g. 'TCS' or 'Tata Consultancy'
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety. The description adds detail about return format (JSON with results array, empty array on no match) and the relative URL structure, which provides helpful behavioral 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 extremely concise and well-structured with separate sections for Args, Returns, Examples, and Error Handling. Every sentence adds value; no redundant or vague language.

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 search tool with one parameter and high schema coverage, the description is fully complete. It covers purpose, usage, return format, error behavior, and integration with sibling tools. No gaps remain for an agent to guess.

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 coverage is 100%, with the single 'query' parameter already described. The description adds value by providing concrete examples ('TCS', 'Infosys', 'HDFC Bank') and specifying the max length (100 chars) from schema, helping agents choose correct input format.

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 searches Screener.in for listed Indian companies by name or ticker symbol. It distinguishes from sibling tools by indicating this is the first step when unsure of the exact identifier, and specifies the output contains 'id', 'name', and 'url' for use with other screener tools.

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?

Explicit guidance is provided: use when unsure of exact ticker, and don't use when you already have the ticker (instead call screener_get_company_overview directly). Examples reinforce correct usage.

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