Skip to main content
Glama
gst-tax-mcp

gst-tax-mcp

by zoeb-nomi

gst_filing_deadlines

Get GST filing due dates for a specified month, quarter, or financial year by filer type, so you can plan returns and avoid late submissions.

Instructions

Filing due dates for a period. period is "YYYY-MM" (month or IFF), "YYYY-Q1".."YYYY-Q4" (quarter), or "FY2026-27" (annual + ITR). filer_type: monthly | qrdp | composition.

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": {
      "period": "<period>"
    },
    "name": "gst_filing_deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodYes
filer_typeNomonthly
state_codeNo27
turnover_above_5crNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only lookup but does not disclose whether results are statutory, authority-dependent, jurisdiction-sensitive, or how they should be interpreted.

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 short, front-loaded, and every sentence carries parameter-format information. The dense formatting and unexplained abbreviation 'IFF' slightly reduce clarity, but there is little wasted wording.

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

Completeness2/5

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

For a four-parameter tool with no annotations, no output schema, and no schema descriptions, the definition leaves major gaps. It explains `period` and `filer_type` but says nothing about `state_code`, `turnover_above_5cr`, or what the caller should expect back.

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 description coverage is 0%, so the description must explain parameters. It usefully defines the `period` formats and lists `filer_type` values, but it completely omits the meaning and effect of `state_code` and `turnover_above_5cr`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific resource and intent: filing due dates for a period. It does not explicitly distinguish this tool from siblings such as calc_gst_liability or gst_applicability, but the resource is distinct enough for an agent to identify it.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance. Usage is only implied by the phrase 'Filing due dates for a period.'

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