Skip to main content
Glama
india-company-diligence

india-company-diligence

Company Lookup

company_lookup

Retrieve a company's details by its 21-character Corporate Identity Number. Use it to identify the registered entity behind a CIN from India's MCA master data.

Instructions

Look up one company by its 21-character Corporate Identity Number.

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

Input Schema

NameRequiredDescriptionDefault
cinYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full load. 'Look up' communicates a non-mutating read and '21-character' flags an input validity constraint, but it says nothing about behavior for a malformed or non-existent CIN (error vs empty result) or whether a lookup counts against any quota.

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?

A single sentence with no filler, and the key scoping word ('one company') plus the input constraint are both front-loaded.

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 (one required string param) and an output schema exists, so return values need no explanation. Still missing is the CIN format detail that would prevent malformed calls, and any routing cue against the three sibling tools that handle adjacent identity tasks.

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 coverage is 0% — the schema only declares 'cin' as a bare string, so any meaning must come from the description. The description adds the 21-character length constraint, which is real value, but omits the actual CIN structure (listing/state/year/ownership segments) or an example, leaving an agent to guess the acceptable format.

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 ('look up') and resource ('one company'), and the word 'one' implicitly contrasts with the sibling company_search which presumably returns multiple. It does not explicitly name that sibling, so an agent must infer the distinction rather than read it.

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 only implied: call it when you already hold a CIN for a single company. There is no explicit when-to-use, no statement of what to do when you have a name instead, and no pointer to company_search, cin_decode, or gstin_validate as alternatives.

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