Fast GST Refund

List the fields of Statement 3 JSON

get_statement3_requirements

Read-onlyIdempotent

Returns the fields of 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, and where each value comes from: export invoices and notes, bank BRC/FIRC rows, and shipping details for goods. Takes no input. Use it before validate_statement3 to learn which fields to collect.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`scope`	No
`checks`	No
`limits`	No
`sha256`	No
`sources`	Yes
`utility`	No
`accepted`	No
`document`	Yes
`workflow`	Yes
`references`	No
`inputSchema`	Yes
`jsonVersion`	No
`notIncluded`	No
`utilityVersion`	No
`generatorVersion`	No
`fieldRulesBySupplyType`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 6, 2026

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: +{
+  "accepted": {
+    "additionalProperties": true,
+    "properties": {
+      "amounts": {
+        "type": "string"
+      },
+      "dates": {
+        "type": "string"
+      },
+      "existingFiles": {
+        "type": "string"
+      },
+      "periods": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "checks": {
+    "type": "string"
+  },
+  "document": {
+    "type": "string"
+  },
+  "fieldRulesBySupplyType": {
+    "additionalProperties": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "object"
+  },
+  "generatorVersion": {
+    "type": "string"
+  },
+  "inputSchema": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "jsonVersion": {
+    "type": "string"
+  },
+  "limits": {
+    "additionalProperties": true,
+    "properties": {
+      "requestBytes": {
+        "type": "number"
+      },
+      "rowsPerFile": {
+        "type": "number"
+      },
+      "splitUploads": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "notIncluded": {
+    "type": "string"
+  },
+  "references": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "scope": {
+    "type": "string"
+  },
+  "sha256": {
+    "type": "string"
+  },
+  "sources": {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "fields": {
+          "type": "string"
+        },
+        "source": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "fields",
+        "source"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "utility": {
+    "type": "string"
+  },
+  "utilityVersion": {
+    "type": "string"
+  },
+  "workflow": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}

removedOutput schema / propertyNames

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

addedOutput schema / required

Added value: +[
+  "document",
+  "workflow",
+  "sources",
+  "inputSchema"
+]

AddedOct 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds genuinely useful context beyond them: that it takes no input and, importantly, the provenance of each field (export invoices/notes, bank BRC/FIRC rows, shipping details), which shapes what the agent can expect to collect.

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-loaded with the purpose, followed by the data-source detail and the usage directive. The first sentence is dense but every clause earns its place; only the domain-specific parentheticals add mild weight.

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 spelled out. For a no-param informational tool, the description fully covers what it returns, that it needs no input, and how it fits before validation.

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?

The tool takes zero parameters, so the baseline is 4. The description reinforces this with "Takes no input," leaving nothing ambiguous about invocation.

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 (Returns) and resource (the fields of the Statement 3 JSON), scoped to a concrete domain output (RFD-01). It is clearly distinguishable from validate_statement3 and generate_statement3, which act on that data rather than enumerate its fields.

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?

"Use it before validate_statement3 to learn which fields to collect" gives explicit ordering and names the alternative it complements. It doesn't state when NOT to use it, but the context is unambiguous for a pre-validation discovery tool.

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.