Skip to main content
Glama
Sign In
mcp-india-stack

mcp-india-stack

by rehan1020
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

validate_aadhaar

Read-onlyIdempotent

Validate Indian Aadhaar numbers by checking 12-digit format and Verhoeff checksum for KYC, identity verification, and benefit workflows. Returns validity and checksum result.

Instructions

Validate an Indian Aadhaar number with Verhoeff checksum verification.

Use when checking Aadhaar format and checksum in KYC, identity verification, or government benefit workflows.

Args: aadhaar: 12-digit Aadhaar number. Spaces and hyphens are stripped.

Returns: Standard envelope containing validity, checksum result, formatted display, and first-digit check.

Notes: Validates format and Verhoeff checksum only. Not connected to UIDAI. In compliance with the Digital Personal Data Protection Act, 2023 (DPDP Act) and UIDAI guidelines, raw Aadhaar numbers are never stored, logged, or exposed.

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

Input Schema

NameRequiredDescriptionDefault
aadhaarYes12-digit Aadhaar number. Spaces and hyphens accepted. Example: 2959 4583 7261

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / aadhaar / title
      Added value: +"Aadhaar"
    • addedInput schema / title
      Added value: +"validate_aadhaarArguments"
    • addedOutput schema / title
      Added value: +"validate_aadhaarDictOutput"
  2. First observedv0.3.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/closed-world annotations by disclosing what is actually checked (format + Verhoeff only, no UIDAI lookup) and a privacy behavior an agent must know: raw Aadhaar numbers are never stored, logged, or exposed under DPDP Act 2023. The Returns line also names the envelope fields, though an output schema exists.

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 one-sentence purpose followed by clearly labeled Use/Args/Returns/Notes sections, which is easy to scan. The Returns block partially duplicates the output schema and the compliance sentence is long, but neither is noise for a KYC-adjacent tool.

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

Completeness5/5

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

For a single-parameter, read-only validator with a full schema and an output schema, the description covers everything an agent needs: what is validated, what is not, call context, input normalization, and the privacy guarantee.

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

Parameters4/5

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

Schema coverage is 100% and already documents the 12-digit format, space/hyphen acceptance, and an example, so the baseline is 3. The description adds one genuine piece of meaning beyond it: spaces and hyphens are 'stripped' (normalization happens), not merely tolerated.

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 an Indian Aadhaar number') plus the exact algorithm ('Verhoeff checksum verification'). The Notes clarify this is format/checksum only and not UIDAI-connected, which implicitly separates it from verify_aadhaar_offline_artifact and, with the singular input, from bulk_validate_aadhaar.

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?

Gives explicit usage contexts: KYC, identity verification, and government benefit workflows. It also bounds scope with 'Validates format and Verhoeff checksum only. Not connected to UIDAI,' but never names a sibling alternative (bulk_validate_aadhaar, verify_aadhaar_offline_artifact) that an agent should pick instead.

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