Fast GST Refund

Read a GST refund guide

read_refund_guide

Read-onlyIdempotent

Returns one public guide as Markdown, with its source links and the date its sources were checked. Takes a slug from search_refund_guides.

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": {
      "slug": "<slug>"
    },
    "name": "read_refund_guide"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes

Output Schema

Name	Required	Description	Default
`url`	Yes
`slug`	Yes
`title`	Yes
`topic`	No
`checked`	No
`markdown`	Yes
`createFiles`	No
`description`	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: +{
+  "checked": {
+    "type": "string"
+  },
+  "createFiles": {
+    "type": "string"
+  },
+  "description": {
+    "type": "string"
+  },
+  "markdown": {
+    "type": "string"
+  },
+  "slug": {
+    "type": "string"
+  },
+  "title": {
+    "type": "string"
+  },
+  "topic": {
+    "type": "string"
+  },
+  "url": {
+    "type": "string"
+  }
+}

removedOutput schema / propertyNames

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

addedOutput schema / required

Added value: +[
+  "slug",
+  "title",
+  "url",
+  "markdown"
+]

First observedOct 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations cover safety (readOnly, idempotent, non-destructive), so the bar is lower. The description adds valuable context about output format (Markdown) and that source links and a checked date are included, which goes beyond the annotations.

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 tight sentences: first states what is returned and its components, second explains the param source. Zero waste and front-loaded.

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?

With an output schema likely detailing the return structure, the description need not enumerate fields, but it helpfully mentions Markdown, source links, and checked date. Combined with annotations covering safety and a single parameter explained, the definition is nearly complete.

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 0%, but with only one parameter (slug) the description successfully clarifies its origin (search_refund_guides). It doesn't repeat the pattern/maxLength from schema, but the origin is the key semantic the schema omits.

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), resource (one public guide), and format (Markdown), plus two extra returned artifacts. It clearly distinguishes itself from search_refund_guides by naming it as the source of the slug.

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?

Tells the agent the slug comes from search_refund_guides, which implies the workflow (search then read). No explicit when-not-to-use guidance, but the context is clear for a single-param retrieval 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.