Skip to main content
Glama

Tapetide - Indian Stock Market MCP

Search Indian Stocks

search_stocks
Read-onlyIdempotent

Search ~8,000 Indian stocks by name, symbol, BSE code, or ISIN. Also matches common/brand names and post-rename aliases (e.g. 'Zomato'→ETERNAL, 'Infosys'→INFY). Listed companies rank first, then by match (exact symbol/code > prefix > word > contains), larger companies first within each; queries of 4+ characters tolerate typos. Each result's symbol is what the per-stock tools take as input.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_stocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10, max 50)
queryNoREQUIRED. The search text — a company name, symbol, BSE code, or ISIN. Example: "reliance" or "TCS".
sectorNoFilter by sector (e.g. 'Information Technology')
industryNoIndustry, exact match (NSE label, e.g. 'Banks'; some rows still use older labels like 'Private Bank')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / industry / description
      Previous value: -"Industry, exact match (NSE label, e.g. 'Banks'; some rows still use vendor labels like 'Private Bank')"New value: +"Industry, exact match (NSE label, e.g. 'Banks'; some rows still use older labels like 'Private Bank')"
  2. Changed1 schema field changed
    • changedInput schema / properties / industry / description
      Previous value: -"Filter by industry (e.g. 'Private Bank')"New value: +"Industry, exact match (NSE label, e.g. 'Banks'; some rows still use vendor labels like 'Private Bank')"
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, closed-world safety, and the description adds substantial behavior beyond them: result ranking (listed first, exact symbol/code > prefix > word > contains, larger companies first) and fuzzy-match tolerance only for queries of 4+ characters. That tells the agent how to interpret ordering and how to craft queries, which is exactly the value-add a description should provide.

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?

Four dense sentences with no filler: dataset scope and searchable fields first, then matching/aliasing, then ranking and typo behavior, then the symbol-chaining hint. Each sentence carries distinct operational information.

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

Completeness4/5

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

With 4 fully documented params, no output schema, and safety covered by annotations, the description is close to complete for a search tool: scope, matching, ranking, and downstream usage are all present. It omits any note on how sector/industry filters interact with ranking and does not flag that query is effectively required despite the schema's 0 required parameters.

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%, so baseline is 3; the description still adds meaning beyond the schema by explaining that query matches aliases and brand names and tolerates typos at 4+ characters, which the schema's one-line query description does not convey. Sector and industry filters are left entirely to the schema, hence not a 5.

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 (search ~8,000 Indian stocks) and enumerates the exact keyable fields: name, symbol, BSE code, ISIN, plus brand names and post-rename aliases. This distinguishes it clearly from siblings like search_investors, screen_stocks, and get_trending_stocks without the agent needing to open schemas.

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

Usage Guidelines4/5

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

Gives strong downstream context: 'Each result's symbol is what the per-stock tools take as input', telling the agent this is the resolution step before get_live_quote/get_financials. It does not explicitly state when to prefer screen_stocks or get_trending_stocks instead, so there is no exclusion guidance, but the use case is unmistakable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.