Skip to main content
Glama
Sign In
india-company-diligence

india-company-diligence

by amit043
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Cin Decode

cin_decode

Decode a Corporate Identity Number offline to extract registration details without network or mirror access.

Instructions

Decode a Corporate Identity Number without using the mirror or network.

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

Input Schema

NameRequiredDescriptionDefault
cinYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that decoding is local and does not use the mirror or network, but it says nothing about error behavior, input validation, or whether the operation is purely read-only.

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?

The description is a single front-loaded sentence with no redundant text. Its brevity is appropriate structurally, even though the content is incomplete elsewhere.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. However, for an offline decoder with no annotations and 0% schema description coverage, the description should clarify expected CIN format and failure behavior; those gaps remain.

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?

There is one required parameter, cin, and schema description coverage is 0%. The description identifies it as a Corporate Identity Number but adds no format, length, or validation details to compensate for the undocumented 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?

The description states a specific verb and resource: decode a Corporate Identity Number. The phrase 'without using the mirror or network' distinguishes it from likely online lookup siblings, though it does not explicitly name company_lookup or company_search.

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?

The description implies this is for offline CIN decoding, but it gives no explicit guidance on when to choose this tool over company_lookup, company_search, or gstin_validate. There are no exclusions or alternative-routing instructions.

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