Skip to main content
Glama
gst-tax-mcp

gst-tax-mcp

by zoeb-nomi

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
gst_applicabilityB

Does this business need GST registration, and is it eligible for the composition scheme? profile is a JSON object (or path to one): aggregate_turnover_prior_fy, state_code, supplies_goods, supplies_services, inter_state_supply, sells_via_ecommerce, casual_taxable_person, composition_scheme_interest.

classify_hsn_sacB

Classify an HSN (goods) or SAC (services) code and return the GST rate in force on the given date (default today), with the rate history.

calc_gst_liabilityA

Compute GST for an invoice. invoice is a JSON object (or file path) with lines: [{description, hsn_sac, quantity, unit_price, discount, place_of_supply_state, supplier_state, reverse_charge, on_date(optional ISO date)}]. Returns per-line tax and totals (CGST/SGST or IGST, cess, reverse-charge liability).

reconcile_itc_toolB

Reconcile input tax credit in the books against GSTR-2B. Each of books and gstr2b is a JSON array (or a file path): rows of {supplier_gstin, invoice_number, invoice_date, taxable_value, itc_amount, hsn_sac}. Flags missing invoices, mismatches beyond tolerance rupees and section 17(5) blocked credits.

gst_filing_deadlinesC

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.

gstr1_summary_toolB

Summarise an outward-supply register into GSTR-1 table buckets (B2B, B2C large, B2C others, exports, SEZ, credit/debit notes, HSN memo). invoices is a JSON array (or file path).

validate_einvoice_toolA

Validate an e-invoice payload: IRN hash format, GSTIN format and checksum, mandatory fields, HSN digit requirements for the supplier's aggregate turnover (supplier_ato), tax math and invoice totals.

itr_turnover_reconcile_toolB

ITR crossover: reconcile GSTR-3B annual turnover against the ITR gross receipts; flags variance beyond 5% and presumptive-limit breaches.

itr_advance_tax_estimate_toolB

ITR crossover: estimate the annual tax and quarterly advance-tax instalments from a projected annual income (new or old regime), and compare regimes.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 9 tools

Disambiguation4/5

Each tool targets a distinct step in the GST/ITR workflow: applicability, classification, liability calc, ITC reconciliation, deadlines, GSTR-1 summary, e-invoice validation, and two ITR tools. The only mild overlap is between reconcile_itc_tool and itr_turnover_reconcile_tool, but the descriptions clearly separate ITC-vs-GSTR-2B from turnover-vs-ITR, so confusion is unlikely.

Naming Consistency2/5

Casing is uniformly snake_case, but the verb convention is chaotic: gst_applicability and gst_filing_deadlines have no verb, classify_hsn_sac and calc_gst_liability lead with an abbreviated verb, reconcile_itc_tool, gstr1_summary_tool, and validate_einvoice_tool append a '_tool' suffix, while itr_turnover_reconcile_tool and itr_advance_tax_estimate_tool put the noun first with the verb embedded mid-name. No single predictable pattern an agent can rely on.

Tool Count5/5

Nine tools is well within the sweet spot for a domain-aware server, and each covers a genuinely distinct compliance function rather than padding the surface. Nothing feels redundant or thin.

Completeness4/5

The surface covers registration, classification, liability, ITC reconciliation, deadlines, GSTR-1, e-invoice validation, and ITR crossovers—a broad lifecycle. Minor gaps exist (no GSTR-3B summary/filing helper, GSTR-9 annual reconciliation, or liability payment/challan step), but agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessOutdated data