Skip to main content
Glama
mcp-india-stack

mcp-india-stack

bulk_validate_aadhaar

Read-onlyIdempotent

Validate up to 500 Aadhaar numbers in parallel for KYC, onboarding, and compliance checks, returning masked per-number results and valid/invalid counts.

Instructions

Validate multiple Aadhaar numbers in parallel using ThreadPoolExecutor.

Use when batch-validating Aadhaar numbers for KYC, onboarding, or compliance workflows.

Args: numbers: List of Aadhaar numbers (with or without spaces/hyphens).

Returns: Standard envelope with per-Aadhaar results and valid/invalid counts.

Notes: Max 500 Aadhaars per call. Uses same Verhoeff validation as single tool. Not connected to UIDAI. In compliance with DPDP Act 2023, results are masked and raw numbers are never stored or logged.

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": {
      "numbers": "<numbers>"
    },
    "name": "bulk_validate_aadhaar"
  }
}

Input Schema

NameRequiredDescriptionDefault
numbersYesList of Aadhaar numbers to validate (max 500)

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 / numbers / title
      Added value: +"Numbers"
    • addedInput schema / title
      Added value: +"bulk_validate_aadhaarArguments"
    • addedOutput schema / title
      Added value: +"bulk_validate_aadhaarDictOutput"
  2. Addedv0.4.2

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description adds substantive behavioral facts: a 500-item ceiling, parallel execution via ThreadPoolExecutor, that validation is offline ('Not connected to UIDAI'), and that outputs are masked with raw numbers never stored or logged under DPDP Act 2023. These are exactly the privacy and capacity constraints an agent needs before sending PII in bulk.

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?

Front-loaded with the verb and resource, then cleanly sectioned into usage, Args, Returns, and Notes. Every line carries information: input format, output shape, limits, and compliance posture. The ThreadPoolExecutor mention is mildly implementation-flavored but signals the concurrency model, so it earns its place.

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 one-parameter bulk tool with an output schema already defining the return envelope, this covers the remaining unknowns: item cap, input formatting, offline nature, and masking behavior. Nothing an agent needs in order to call it safely is absent.

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% for the single array parameter, so the baseline is 3, but the description adds genuine formatting tolerance the schema lacks: 'with or without spaces/hyphens.' It also restates the 500 cap per element context, giving the agent concrete input-shaping guidance beyond the schema's bare type declaration.

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?

The description opens with a specific verb and resource ('Validate multiple Aadhaar numbers in parallel') and explicitly distinguishes itself from the single-record alternative by noting it 'Uses same Verhoeff validation as single tool.' An agent can immediately tell this is the batch counterpart to validate_aadhaar in the sibling list.

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?

It names concrete use contexts ('KYC, onboarding, or compliance workflows') and states the hard limit of 'Max 500 Aadhaars per call.' What's missing is an explicit routing statement such as 'for a single number use validate_aadhaar', leaving that inference to the name alone, which is why this is a 4 rather than 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