Fast GST Refund

Check records for Annexure B JSON

validate_annexure_b

Read-onlyIdempotent

Checks records for the Annexure B JSON (statement of inward-supply invoices) for a GST refund of accumulated ITC (RFD-01), the file the GST portal otherwise requires from its Excel offline utility. Applies the offline utility's own checks and returns every error and warning at once, with its row and field. Free; needs no sign-in; stores nothing. A file made by the official utility can be passed as data unchanged. ITC eligibility, reversal amounts and GSTR-2B periods come from the taxpayer's reviewed records; the tool does not infer them.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	The document's fields, as its requirements tool lists them, or a JSON file from the official utility unchanged.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`claim`	No
`valid`	Yes
`errors`	Yes
`message`	No
`summary`	No
`document`	Yes
`nextStep`	No
`warnings`	Yes
`inputFormat`	No
`jsonVersion`	No
`utilityVersion`	No
`generatorVersion`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 6, 2026

removedInput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / data / additionalProperties
```
Previous value: -{}New value: +true
```
removedInput schema / properties / data / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties
```
Previous value: -{}New value: +true
```

addedOutput schema / properties

Added value: +{
+  "claim": {
+    "additionalProperties": true,
+    "properties": {
+      "fromFp": {
+        "type": "string"
+      },
+      "gstin": {
+        "type": "string"
+      },
+      "paid": {
+        "type": "boolean"
+      },
+      "toFp": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "document": {
+    "type": "string"
+  },
+  "errors": {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "path": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "path",
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "generatorVersion": {
+    "type": "string"
+  },
+  "inputFormat": {
+    "type": "string"
+  },
+  "jsonVersion": {
+    "type": "string"
+  },
+  "message": {
+    "type": "string"
+  },
+  "nextStep": {
+    "type": "string"
+  },
+  "summary": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "utilityVersion": {
+    "type": "string"
+  },
+  "valid": {
+    "type": "boolean"
+  },
+  "warnings": {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "path": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "path",
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+}

removedOutput schema / propertyNames

Removed value: -{
-  "type": "string"
-}

addedOutput schema / required

Added value: +[
+  "document",
+  "valid",
+  "errors",
+  "warnings"
+]

AddedOct 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description adds real operational context: free, no sign-in, stores nothing, and returns every error and warning at once with row and field. It also discloses a key boundary — ITC eligibility, reversal amounts and GSTR-2B periods are taken from the taxpayer's reviewed records and are not inferred.

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?

Purpose is front-loaded and every sentence carries information (scope, behavior, cost/auth, input expectation, non-inference caveat). It is somewhat dense at four sentences, but there is no filler or repetition.

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

Completeness5/5

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

An output schema exists, so return values need not be detailed, and the annotations cover safety semantics. The description still covers scope, side effects, auth/privacy, input expectations and inference boundaries — nothing needed to invoke it correctly is missing.

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% for the single 'data' parameter, so the baseline is 3. The description adds meaning beyond the schema by stating the official utility's file can be passed unchanged and that eligibility/reversal/period values are not inferred, clarifying what the caller must supply.

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 specific verb and resource ('Checks records for the Annexure B JSON') and anchors it in the refund domain (RFD-01, inward-supply invoices). It is clearly distinguishable from siblings such as generate_annexure_b, get_annexure_b_requirements and validate_statement3.

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?

The description establishes when it applies ('A file made by the official utility can be passed as data unchanged', validating before the portal requires it), which gives a clear operating context. It never explicitly names an alternative tool or states when NOT to use it, so it stops short of full routing guidance.

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

All Fast GST Refund tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.