Skip to main content
Glama

Parse AIS (Annual Information Statement)

parse_ais
Read-only

Decrypt and parse AIS JSON files from the Indian income tax portal on your device. Supply PAN and date of birth to derive the password, or provide it directly, to extract taxpayer information and normalized transaction entries.

Instructions

Decrypt and parse the AIS JSON export from the income tax portal, entirely on-device. Provide pan + dob (DDMMYYYY) to derive the password, or pass it explicitly. Returns taxpayer info and normalized information rows (TDS entries, SFT transactions) with amounts, dates, and codes extracted by column label. The decryption scheme is reverse-engineered from the AIS utility; if it fails, use the portal's CSV export as a fallback and file an issue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dobNoDate of birth as DDMMYYYY (or DD-MM-YYYY); date of incorporation for non-individuals
panNoPAN (used to derive the decryption password)
pathYesAbsolute path to the downloaded AIS .json file
passwordNoExplicit decryption password (overrides pan+dob derivation)
Behavior4/5

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

Beyond annotations (readOnlyHint, openWorldHint), the description discloses on-device processing, reverse-engineered decryption, fallback behavior, and the structure of returned data. No contradictions with annotations.

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?

The description is reasonably concise, with two sentences covering key aspects. It front-loads the main action, though it could be slightly tighter without losing substance.

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 no output schema and moderate complexity (4 params, 1 required), the description provides comprehensive context: inputs, output structure, decryption details, fallback, and error handling. Fully sufficient.

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%, so the description adds only marginal value by clarifying the relationship between pan/dob and password derivation. The baseline of 3 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 explicitly states the tool decrypts and parses AIS JSON exports, specifies required inputs (pan, dob) and outputs (taxpayer info, normalized rows). It distinguishes itself from potential siblings like parse_form26as by focusing on AIS specifically.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when handling AIS JSON exports and mentions a fallback (CSV export), but does not explicitly differentiate from sibling tools like parse_form26as or provide when-not-to-use guidance.

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/Sagargupta16/itr-mcp'

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