Skip to main content
Glama
gst-tax-mcp

gst-tax-mcp

by zoeb-nomi

reconcile_itc_tool

Reconciles input tax credit in books against GSTR-2B, flagging missing invoices, value mismatches beyond tolerance, and section 17(5) blocked credits.

Instructions

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.

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": {
      "books": "<books>",
      "gstr2b": "<gstr2b>"
    },
    "name": "reconcile_itc_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
booksYes
gstr2bYes
toleranceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the analytical behavior: it flags missing invoices, tolerance-exceeding mismatches, and section 17(5) blocked credits. However, it does not state that the operation is non-mutating, does not describe error handling for malformed JSON or unreadable file paths, and does not cover performance or scale expectations.

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?

Three tight sentences, front-loaded with the action, then the input contract, then the outputs. The inline row-schema enumeration is dense but earns its space given 0% schema coverage; minor readability cost from cramming it into a parenthetical sentence.

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

Completeness3/5

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

For a three-parameter, no-annotation, no-output-schema tool, the description covers inputs well and hints at outputs (missing invoices, tolerance-breach mismatches, blocked credits) but does not describe the shape of the reconciliation result. An agent knows how to call it but only roughly what it will get back.

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

Parameters4/5

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

Schema coverage is 0% — all three parameters have only bare titles — so the description must compensate, and it largely does: it explains that books and gstr2b accept either a JSON array or a file path and enumerates the exact row fields (supplier_gstin, invoice_number, invoice_date, taxable_value, itc_amount, hsn_sac). Tolerance is given meaning and units ('mismatches beyond tolerance rupees') but its default and comparison direction are not spelled out.

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?

States a specific verb and resource: reconcile input tax credit in the books against GSTR-2B. The named counterpart (GSTR-2B) distinguishes it from turnover- or GSTR-1-oriented siblings, though the description never explicitly routes away from any alternative.

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 statement, no prerequisite (e.g. period, GSTIN scope, filing stage), and no pointer to any sibling tool such as itr_turnover_reconcile_tool or calc_gst_liability. The mention of missing invoices and mismatches describes outputs, not invocation conditions.

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