Skip to main content
Glama
rehan1020

mcp-india-stack

by rehan1020
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_regulatory_deadlines

Read-onlyIdempotent

Get India's tax and regulatory compliance deadlines for FY2025-26. Filter by category or date to plan filings, deposits, and returns for ITR, TDS, GST, PF/ESIC, ROC, and more.

Instructions

Get India's tax & regulatory compliance calendar for FY2025-26.

Use when planning tax compliance schedules, setting reminders for deadlines, or building financial compliance dashboards.

Args: category: Filter by category (Income Tax, TDS, GST, PF/ESIC, ROC, etc.) from_date: Start date filter (YYYY-MM-DD) to_date: End date filter (YYYY-MM-DD)

Returns: Standard envelope with deadlines grouped by month for FY2025-26

Notes: Covers ITR filing, TDS deposits, GST returns, PF/ESIC, ROC filings, advance tax, and professional tax deadlines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
to_dateNoEnd date filter (YYYY-MM-DD)
categoryNoFilter by category (Income Tax, TDS, GST, PF/ESIC, ROC, etc.)
from_dateNoStart date filter (YYYY-MM-DD)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / category / title
      Added value: +"Category"
    • addedInput schema / properties / from_date / title
      Added value: +"From Date"
    • addedInput schema / properties / to_date / title
      Added value: +"To Date"
    • addedInput schema / title
      Added value: +"get_regulatory_deadlinesArguments"
    • addedOutput schema / title
      Added value: +"get_regulatory_deadlinesDictOutput"
  2. Addedv0.4.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the tool read-only and idempotent. The description adds useful behavioral context beyond that: results are 'deadlines grouped by month' and the coverage spans ITR, TDS, GST, PF/ESIC, ROC, advance tax, and professional tax. This goes beyond the structured hints without contradicting them.

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?

The description is compact and scannable, with a front-loaded summary followed by short Args, Returns, and Notes sections. Every line contributes information: scope, use cases, parameters, return format, and covered compliance types.

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 an output schema exists, the description does not need to detail return fields. It clearly communicates the fiscal year, optional filters, return shape ('standard envelope with deadlines grouped by month'), and regulatory coverage. This is sufficient for an agent to select and call the tool correctly.

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?

Input schema descriptions cover 100% of parameters, so the description is not required to carry the full burden. The Args section largely repeats the schema, including category examples and YYYY-MM-DD date formats, without adding deeper semantics such as allowed category enumeration or date boundary behavior. Baseline 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 states a clear verb-resource pair: 'Get India's tax & regulatory compliance calendar for FY2025-26.' It names the exact domain, fiscal year, and deliverable, distinguishing it from the sibling tools, which are mostly validators and calculators rather than calendar/deadline queries.

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?

Provides explicit context for when to use the tool: 'planning tax compliance schedules, setting reminders for deadlines, or building financial compliance dashboards.' It does not name alternatives or exclusion criteria, but no sibling offers comparable deadline-calendar functionality, so clear context is sufficient.

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