Fast GST Refund

Find GST refund guidance

search_refund_guides

Read-onlyIdempotent

Finds Fast GST Refund's public guides by preparation topic and returns their slugs, titles and descriptions. Takes general keywords; it does not need taxpayer identifiers or document contents.

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes

Output Schema

Name	Required	Description	Default
`guides`	Yes

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: +{
+  "guides": {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "description": {
+          "type": "string"
+        },
+        "slug": {
+          "type": "string"
+        },
+        "sourcesChecked": {
+          "type": "string"
+        },
+        "title": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "slug",
+        "title",
+        "url"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+}

removedOutput schema / propertyNames

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

addedOutput schema / required
```
Added value: +[
+  "guides"
+]
```

First observedOct 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and a closed (non-open-world) corpus. The description adds that the corpus is public guides and that no sensitive inputs are required, which is genuinely useful but not deep. Return values are covered by the output schema, so little else is owed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, and the primary function plus return shape is front-loaded before the input constraint. Nothing redundant with the annotations or schema is repeated.

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?

An output schema exists, so return values need not be explained, and the description confirms them anyway. For a read-only, non-open-world search tool the picture is largely complete, with the only gap being the undocumented 'limit' parameter and absent routing to read_refund_guide.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It clarifies that 'query' takes general keywords, but 'limit' is never mentioned and no format, matching behavior, or maxLength/pattern constraints are explained beyond what the raw schema shows.

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 (Finds), the exact resource (Fast GST Refund's public guides), the retrieval axis (by preparation topic), and the return shape (slugs, titles, descriptions). This clearly separates it from read_refund_guide, which presumably fetches a single guide.

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 contextually implies keyword search over public guides and rules out needing taxpayer identifiers or document contents, which is useful scoping. However, it never says when to prefer this over the sibling read_refund_guide (e.g., discover-then-read), so routing guidance is only implied.

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.