Skip to main content
Glama
screener-mcp
by LogeshR15

search_company

Read-only

Find an Indian listed company by name or NSE/BSE symbol to locate stocks for financial research and screening.

Instructions

Search for an Indian stock/company by name or NSE/BSE symbol.

Examples: search_company("Tata Consultancy") search_company("INFY") search_company("Jyothy Labs") search_company("ITC")

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the NSE/BSE symbol scope but says nothing about matching behavior (fuzzy vs exact, multiple matches, empty results); an output schema exists, so return shape need not be described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One scoping sentence followed by compact examples; every example adds a distinct input pattern rather than restating the same case. The block is slightly padded but front-loaded and earns its space for an ambiguous free-text parameter.

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?

For a one-parameter lookup with an output schema, annotations, and worked examples, the definition covers what an agent needs to call it. The only real gap is guidance on ambiguous or failed matches, which is minor.

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 0% for the single 'query' parameter, so the description must carry the load. The examples do this well by demonstrating a full company name, a bare ticker ('INFY'), a partial/multi-word name, and a short symbol ('ITC'), implying flexible name-or-symbol input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search for an Indian stock/company') plus the two accepted identifier kinds (name, NSE/BSE symbol). An agent can tell it is a lookup tool, though it does not explicitly separate itself from siblings like get_company_overview or screen_stocks.

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

Usage Guidelines3/5

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

The four example calls implicitly show when this tool fits (you have a company name or ticker and need to resolve it) and illustrate acceptable input forms including partial names. There is no explicit statement of when NOT to use it or which sibling to pick instead.

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