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

india-company-diligence

by amit043
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Gstin Validate

gstin_validate

Validates GSTIN structure, state code, and mod-36 check digit offline; live registration fields are flagged as unavailable rather than fabricated.

Instructions

Validate a GSTIN offline: structure, state code, and mod-36 check digit.

Pure offline — no network, no keys. Live fields (legal name, trade name, registration status, filing history) require an authenticated GST API and are stated as missing, never fabricated.

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

Input Schema

NameRequiredDescriptionDefault
gstinYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the offline/no-key execution model and, importantly, that live fields are 'stated as missing, never fabricated' — a meaningful guarantee about output behavior. It does not say whether an invalid GSTIN raises an error or returns a validity flag, which the output schema partly covers.

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?

Two short paragraphs, front-loaded with the verb and the checks, followed by the trust caveat. Every sentence adds information; nothing is redundant.

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 one string parameter, no annotations, and an output schema present, the definition covers most of what an agent needs. The remaining gap is the expected input format and the failure behavior for a malformed GSTIN.

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%, so the description must compensate. It explains what aspects of the GSTIN are validated, but never states the expected input format (e.g., 15-character alphanumeric, casing rules), which is the key semantic gap for the sole parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Validate a GSTIN offline') and enumerates exactly what is checked: structure, state code, and mod-36 check digit. This makes it clearly distinct from siblings like company_lookup, company_search, and cin_decode without naming them.

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?

Establishes the selection context: offline-capable, no network or keys, and live fields explicitly require an authenticated GST API, which effectively routes the agent elsewhere for those needs. It stops short of naming the sibling tool that provides live data.

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