Fast GST Refund

Check records for Statement 3 JSON

validate_statement3

Read-onlyIdempotent

Checks records for the Statement 3 JSON for a GST refund of accumulated ITC on exports without payment of tax (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.

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.2/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the bar is lower. The description adds real behavioral value beyond them: it returns every error and warning at once with row and field, requires no sign-in, stores nothing, and accepts official utility output unchanged.

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?

Dense but front-loaded: the resource and form are named first, then behavior, then cost/auth/storage in compact clauses. Every sentence earns its place, though the phrasing is somewhat packed.

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?

With an output schema present, return values need not be explained, yet the description still characterizes them. Auth, storage, and input-compatibility concerns are all addressed, making it complete for a single-object validator.

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 already 3+. The description adds meaning beyond the schema by clarifying that an official utility file can be passed unchanged and that it applies the utility's own checks.

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 (checks/validates) and resource (Statement 3 JSON for RFD-01 GST refund), and implicitly contrasts with siblings like generate_statement3 and get_statement3_requirements. An agent can distinguish it from validate_annexure_b by the named form.

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

Usage Guidelines3/5

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

The description implies usage ('Applies the offline utility's own checks', 'a file made by the official utility can be passed as data unchanged') but never states when to use this versus validate_annexure_b or get_statement3_requirements, nor any preconditions. Usage is inferable but not explicit.

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.