Skip to main content
Glama
india-company-diligence

india-company-diligence

Company Search

company_search

Search company names case-insensitively in India MCA master data to retrieve matching records, up to a specified limit, for company diligence.

Instructions

Search company names case-insensitively, returning at most 50 rows.

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": {
      "name": "<name>"
    },
    "name": "company_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
limitNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two real behavioral traits: matching is case-insensitive and results are capped at 50 rows. It omits matching mode (exact/prefix/substring), what happens when limit exceeds 50, and any authorization 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 efficient sentence with the core behavior front-loaded and no wasted words. Its brevity is close to excessive, but nothing in it is filler.

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

Completeness3/5

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

The tool is simple, the output schema exists so return shape need not be explained, and the description covers the essential behavior. Still missing are the meaning of the limit parameter and why an agent would pick this over company_lookup — both needed for correct invocation in this sibling set.

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

Parameters2/5

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

Schema description coverage is 0%, so both parameters are undocumented in the schema. The description implies that "name" is the search term but says nothing about the limit parameter, and the stated 50-row ceiling conflicts ambiguously with a caller-supplied limit (default 10) — the agent cannot tell which wins.

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?

The description states a specific verb and resource ("Search company names") plus a matching rule (case-insensitive), so the agent knows exactly what the tool does. It does not, however, differentiate itself from the sibling company_lookup, leaving the agent to guess which to call.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus company_lookup, which reads like the obvious alternative for name-based retrieval. No prerequisites, exclusions, or selection criteria are given.

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