Skip to main content
Glama
Prem07a
by Prem07a

search_ticker

Find the NSE/BSE ticker symbol for a company by name or partial name. Use this first to convert a company name into its exact Yahoo Finance ticker before other calls.

Instructions

Find the NSE/BSE ticker symbol for a company by name or partial name. Use this first whenever you know a company's name but not its exact Yahoo Finance ticker, before calling any other tool here.

Filters Yahoo's global search results down to Indian-listed equities
only -- a plain name search otherwise mixes in US ADRs, other
exchanges, and non-equity instruments (ETFs, futures).

Two things worth knowing: (1) a company that demerged can have
multiple current tickers for what feels like one name -- e.g.
"Tata Motors" correctly returns two separate post-split entities
(commercial vehicles and passenger vehicles); don't assume a single
match is right without checking `name`/`industry`. (2) a renamed
company won't be found under its old name at all -- e.g. "Zomato"
returns zero matches since the company renamed to "Eternal Limited";
an empty result doesn't necessarily mean the company isn't listed, so
try the company's current/formal name before concluding that.

:param query: company name or partial name, e.g. "Reliance", "Tata Consultancy Services"
:param limit: max number of matches to return (default 10)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoSet when matches is empty: the company may have been renamed, or isn't Indian-listed
queryYes
matchesYes
Install Server

TDQS

A5/5.0
Behavior5/5

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

With no annotations at all, the description must carry the full burden, and it does: it discloses Indian-market filtering, demerger multiple-ticker behavior, renamed-company failures, and the real meaning of empty results.

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?

Although longer than average, every sentence serves a purpose; the core purpose and usage rule are front-loaded, and the behavioral caveats are organized clearly.

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?

Given the output schema exists and annotations are absent, this description provides all essential context an agent needs to call, interpret results, and handle edge cases for this search-first tool.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description fully compensates by defining `query` with examples and `limit` with a default and meaning, adding real semantics beyond the bare schema.

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?

States a specific verb and resource ('Find the NSE/BSE/BSE ticker symbol for a company by name or partial name') and immediately says to use it before any other tool, making it distinct from siblings.

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?

Gives explicit when-to-use guidance ('whenever you know a company's name but not its exact Yahoo Finance ticker, before calling any other tool here') and warns against plain name searches mixing in irrelevant instruments, plus advises trying current/formal names on empty results.

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

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/Prem07a/FinMCP'

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