Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_gst_late_fee

Read-onlyIdempotent

Calculates GST late filing fees for GSTR1, GSTR3B, or GSTR9 returns and shows the CGST/SGST split to help estimate penalties and plan compliance.

Instructions

Calculate GST late filing penalty.

Use when estimating late filing fees or planning compliance.

Args: return_type: "GSTR1", "GSTR3B", or "GSTR9" days_delayed: Number of days delayed annual_turnover: Annual turnover for cap calculation has_nil_liability: True if nil return

Returns: Late fee breakdown with CGST/SGST split.

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": {
      "return_type": "<return_type>",
      "days_delayed": "<days_delayed>",
      "annual_turnover": "<annual_turnover>"
    },
    "name": "calculate_gst_late_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
return_typeYesGSTR1, GSTR3B, or GSTR9
days_delayedYesNumber of days delayed
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
annual_turnoverYesAnnual turnover in INR
has_nil_liabilityNoTrue if nil return

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / financial_year
      Added value: +{
      +  "default": "2025-26",
      +  "description": "Financial year (e.g. '2025-26', '2026-27')",
      +  "title": "Financial Year",
      +  "type": "string"
      +}
  2. Changed7 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / annual_turnover / title
      Added value: +"Annual Turnover"
    • addedInput schema / properties / days_delayed / title
      Added value: +"Days Delayed"
    • addedInput schema / properties / has_nil_liability / title
      Added value: +"Has Nil Liability"
    • addedInput schema / properties / return_type / title
      Added value: +"Return Type"
    • addedInput schema / title
      Added value: +"calculate_gst_late_feeArguments"
    • addedOutput schema / title
      Added value: +"calculate_gst_late_feeDictOutput"
  3. Addedv0.4.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so safety and determinism are covered by structured data. The description adds that annual_turnover drives a cap calculation and that the output splits into CGST/SGST, which is modest extra context but nothing about applicability edge cases or rate rules.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and usage sentences are front-loaded and tight, but the Args and Returns blocks duplicate the input schema and output schema nearly verbatim, which is padding rather than added value. Trimming those blocks would leave a stronger definition.

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

Completeness4/5

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

With five documented parameters, an output schema, and explicit read-only/idempotent annotations, the definition gives an agent everything needed to invoke the tool correctly. The only shortfall is the absence of any note on applicability limits or how the financial_year default interacts with days_delayed.

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 100%, so the baseline is 3. The description's Args block largely restates the schema fields, with only 'annual_turnover for cap calculation' adding real meaning beyond the schema; financial_year is not mentioned in the description at all.

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 opens with a specific verb and resource: 'Calculate GST late filing penalty,' which is clearly distinct from the sibling calculate_gst (tax computation) and calculate_income_tax_interest. It doesn't explicitly name those siblings as alternatives, so it stops short of a 5.

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?

'Use when estimating late filing fees or planning compliance' gives a general usage context, but there is no when-not guidance and no routing to related siblings such as calculate_gst or get_regulatory_deadlines. The usage signal is implied rather than operational.

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