Skip to main content
Glama

Nityaflow GST credit match

Match GSTR-2B with the purchase register

gst_credit_match
Read-onlyIdempotent

India GST input tax credit check. Matches the supplier invoices in GSTR-2B against the purchase register from the books (Tally, Zoho Books, Busy, QuickBooks or any list) and sorts every invoice into: matched, amount mismatch, entered twice (duplicate bills), possible match (invoice number or GSTIN written differently), in books but not in GSTR-2B (credit at risk), in GSTR-2B but not in books. A separate checker re-derives the totals, and the result comes with a receipt signed by Nityaflow. Invoices are processed in memory and not stored. It never files or accepts anything on the GST portal.

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

Input Schema

NameRequiredDescriptionDefault
booksYesPurchase register from the books: a list of invoices like {gstin, invoice, date, name, taxable, igst, cgst, sgst, cess, value}. Use the supplier's bill number, not the voucher number.
clientNoClient or business name, for the receipt.
gstr2bYesGSTR-2B: either the JSON file downloaded from the GST portal, or a list of invoices like {gstin, invoice, date, taxable, igst, cgst, sgst, cess}.
periodNoReturn period, for example 2026-09.
toleranceNoAllowed difference in rupees before amounts count as different. Default 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: invoices are processed in memory and not stored, a separate checker re-derives totals, and a signed receipt is produced. It also states explicitly what the tool will not do (no portal filing), which is exactly the reassurance an agent needs before handling client financial data.

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?

Front-loads the purpose in the first sentence, then the outcome taxonomy, then privacy and safety caveats. The six-category enumeration is long but each item carries decision-relevant information; only the receipt-signing detail is slightly peripheral.

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?

Covers inputs, output categories, data handling and safety limits despite having no output schema. A minor gap: it mentions a signed receipt but not whether verify_receipt is the intended follow-up, leaving the sibling relationship unexploited.

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 100%, so the baseline is 3, but the description adds real meaning: it enumerates concrete source systems (Tally, Zoho Books, Busy, QuickBooks, any list) for the books and clarifies the GSTR-2B input can be either a portal JSON download or a plain list. It does not repeat tolerance or period, which the schema already handles.

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

Purpose5/5

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

States a concrete verb and resource: matches GSTR-2B supplier invoices against the purchase register from the books. The category taxonomy (matched, mismatch, duplicate, possible match, at risk, missing) makes the operation unambiguous and clearly distinct from the sibling verification tools.

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

Usage Guidelines4/5

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

Establishes clear context: an India GST input tax credit reconciliation for a given return period, with accepted books sources named. It also sets a firm boundary ('never files or accepts anything on the GST portal'), but never explicitly contrasts with agent_payment_check or verify_receipt.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources