Skip to main content
Glama
mcp-india-stack

mcp-india-stack

validate_cin

Read-onlyIdempotent

Validate and decode a 21-character Indian CIN to confirm format and extract listing status, NIC code, state, incorporation year, and company type, with optional online registry attestation.

Instructions

Validate and decode an Indian CIN (Company Identification Number).

Use when verifying company registration data, extracting listing status, NIC code, state, year, and company type from a CIN.

Args: cin: 21-character CIN string. Spaces and hyphens stripped automatically. verify_online: Optional opt-in online registry attestation (A4 level).

Returns: Standard envelope containing decoded fields: listing status, NIC code, state, year of incorporation, company type, and serial number.

Notes: Format validation with field decoding. No public checksum.

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

Input Schema

NameRequiredDescriptionDefault
cinYes21-character CIN (spaces/hyphens allowed). Example: L17110MH1973PLC019786
verify_onlineNoOptional opt-in online registry attestation (A4 level)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / verify_online
      Added value: +{
      +  "default": false,
      +  "description": "Optional opt-in online registry attestation (A4 level)",
      +  "title": "Verify Online",
      +  "type": "boolean"
      +}
  2. Changed4 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / cin / title
      Added value: +"Cin"
    • addedInput schema / title
      Added value: +"validate_cinArguments"
    • addedOutput schema / title
      Added value: +"validate_cinDictOutput"
  3. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

The description goes meaningfully beyond the annotations: it discloses that validation is format-only ('No public checksum'), that whitespace and hyphens are stripped before parsing, and that online registry attestation is opt-in via verify_online. The only tension is that verify_online implies an outbound registry call while openWorldHint is false, which the description leaves unexplained rather than contradicts outright.

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 purpose sentence, then clean Args/Returns/Notes sections that an agent can scan quickly. There is mild redundancy in restating CIN length and the verify_online description verbatim from the schema, and the Returns block duplicates the output schema.

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 2-parameter validation tool with full schema coverage, annotations, and an output schema, the description covers everything essential, including the key limitation that validation is format-only with no checksum. The Returns section is redundant given the output schema, but nothing an agent needs before calling is missing.

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 the Args block largely restates the schema ('21-character CIN string', 'Optional opt-in online registry attestation') with the same wording. The whitespace-stripping note is helpful but already appears in the schema's 'spaces/hyphens allowed' text, so added meaning is marginal.

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 opens with a specific verb pair and resource: 'Validate and decode an Indian CIN (Company Identification Number)'. That is unambiguous against siblings like validate_din or validate_pan, since the resource itself is the differentiator, though it never names an alternative explicitly.

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

Usage Guidelines4/5

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

'Use when verifying company registration data, extracting listing status, NIC code, state, year, and company type from a CIN' gives clear trigger context for the tool. It stops short of stating when NOT to use it or which sibling (e.g. decode_isin, validate_llpin) to prefer, so it does not reach a 5.

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

Deploy Server

Other Tools