Skip to main content
Glama

SN Data by Shikshan Nivesh

Find companies

search_companies
Read-onlyIdempotent

Find US companies covered by SN Data by ticker or name, optionally narrowed by industry or index, with the ticker each one is listed under.

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_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNoAn index name, like S&P 500.
limitNoMost companies to return. Default 20.
queryNoPart of a ticker or company name, like NVDA or nvidia.
industryNoPart of an industry name, like Semiconductors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the coverage boundary (only US companies in the SN Data universe) and what comes back ('the ticker each one is listed under'), which is meaningful given there is no output schema. It does not discuss result caps or pagination behavior.

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?

A single front-loaded sentence covering scope, match fields, optional narrowing, and return content with no redundant phrasing. Dense but efficient; it could be split slightly for readability but nothing is wasted.

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 four all-optional parameters, full schema coverage, and annotations covering the safety profile, the description needs only to establish scope and matching behavior, which it does. The one remaining gap is that it never signals the result cap or that results are partial-match ranked, leaving the agent to discover the limit parameter from the schema.

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

Parameters3/5

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

Schema description coverage is 100% and each parameter is documented with an example value, so the schema carries the semantic load. The description restates the same three filter dimensions (ticker/name, industry, index) without adding format or matching-rule detail, and omits the limit parameter entirely, which is baseline behavior for a fully annotated schema.

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 (find) and resource (US companies covered by SN Data), plus the key match fields (ticker or name) and optional narrowing dimensions. It implicitly separates itself from a single-entity lookup like get_company by framing the operation as a search with partial-match inputs, though it never names that sibling.

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?

Usage is implied by 'Find ... by ticker or name, optionally narrowed by industry or index', which tells the agent how to invoke it. There is no explicit when-to-use vs. when-not guidance and no named alternative such as get_company for exact retrieval, so the agent must infer the boundary.

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.

Resources