Skip to main content
Glama
tearsheet

tearsheet

by kewonit

find_company

Read-only

Look up listed Indian companies by NSE symbol, BSE code, or name to resolve ambiguous names and retrieve NSE/BSE identifiers, slugs, and match details.

Instructions

Find a listed Indian company and its identifiers.

    Accepts an NSE symbol, a BSE code, a company name or part of one. Returns
    each match's name, NSE symbol, BSE code and slug, plus what it matched on.
    Use this when a name is ambiguous or you need the identifiers. Other tools
    accept the same input, so you don't need to call this first. An empty
    match list means nothing was found. ISINs aren't available. Check the
    warnings: if the input wasn't a real symbol, they give the actual one.
    

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": "find_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofNo
unitsNo
entityNo
sourcesNo
warningsNo
next_cursorNo
retrieved_atNo
verificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

The readOnlyHint annotation already covers the safety profile, so the description's job is to add context, which it does: empty match list semantics, warnings carrying the corrected symbol, and the unavailability of ISINs. It stops short of describing match ordering or how many matches are returned, but the supplied output schema covers return shape.

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?

Front-loaded with purpose and inputs, then return shape, then usage caveats. Every sentence carries information, though the ISIN and warnings sentences could be tightened slightly for a single-parameter tool.

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 one-parameter read-only resolver with an output schema, nothing an agent needs is missing: input forms, ambiguity handling, empty-result meaning, and the warnings signal are all stated. Return values needn't be re-explained given the output schema exists.

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% — the 'query' property has no description at all — so the description carries the full burden and does: it names the accepted forms (NSE symbol, BSE code, full or partial company name). That is exactly the semantic gap the schema leaves.

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 a listed Indian company and its identifiers') and enumerates the four accepted query forms plus the returned fields (name, NSE symbol, BSE code, slug, match reason). An agent can distinguish this lookup tool from siblings like company_snapshot without opening any schema.

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 an explicit when-to-use condition ('when a name is ambiguous or you need the identifiers') and an explicit when-not ('Other tools accept the same input, so you don't need to call this first'). That removes the most likely misuse pattern for a resolver tool.

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