Skip to main content
Glama
rehan1020

mcp-india-stack

by rehan1020

validate_aadhaar

Read-onlyIdempotent

Verify Indian Aadhaar number format and checksum for KYC, identity verification, or government benefit workflows.

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.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds the Verhoeff checksum algorithm, providing useful behavioral detail beyond annotations.

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 sentences, front-loaded with action and algorithm, followed by usage context. No redundant or vague language.

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?

Given the tool's simplicity, annotations, and output schema, the description is complete: it defines purpose, algorithm, and use cases.

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 100% with a clear parameter description (12-digit, spaces/hyphens, example). The tool description adds no extra parameter info, so baseline score is appropriate.

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 clearly states the tool validates an Aadhaar number using Verhoeff checksum, distinguishing it from sibling tools that validate other Indian identifiers (PAN, GSTIN, etc.).

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?

Explicitly states when to use (KYC, identity verification, government benefits), though no explicit when-not-to-use is given. Context from sibling tools makes it clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rehan1020/MCP-India-Stack'

If you have feedback or need assistance with the MCP directory API, please join our Discord server