Skip to main content
Glama
gst-tax-mcp

gst-tax-mcp

by zoeb-nomi

calc_gst_liability

Calculate GST liability for an invoice from line items, state details, and dates, returning per-line CGST/SGST or IGST, cess, and reverse-charge totals.

Instructions

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).

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": {
      "invoice": "<invoice>"
    },
    "name": "calc_gst_liability"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoiceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the expected input shape and the return payload (per-line tax, CGST/SGST vs IGST split, cess, reverse-charge liability). It stops short of stating whether the tool is a pure computation with no persistence, or how rounding precision and validation failures are handled.

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?

Two sentences, front-loaded with the purpose, then the input contract and return contract. The embedded field list is dense but each item earns its place; the '(or file path)' ambiguity for a string-typed parameter costs a point.

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?

For a single-parameter tool with no output schema, the description covers both the input contract and the shape of the result, which is most of what an agent needs. Gaps remain around numeric precision, currency/rounding conventions, and error behavior for malformed invoices.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the only parameter is an opaque string titled 'Invoice' — so the description must compensate, and it does: it explains that the value is a JSON object or file path and enumerates the line-level fields (hsn_sac, place_of_supply_state, supplier_state, reverse_charge, optional on_date). That is far more meaning than the schema provides.

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, 'Compute GST for an invoice', which reads clearly against siblings such as gst_applicability and classify_hsn_sac. It never explicitly names or excludes a sibling, so differentiation is inferred from the purpose rather than stated.

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?

There is no when-to-use guidance, no preconditions, and no pointer to the sibling tools that handle adjacent tasks (applicability checks, HSN classification, reconciliation). The usage is only implied by the phrase 'for an invoice', leaving the agent to guess when this is the right call versus gst_applicability.

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