Skip to main content
Glama
gst-tax-mcp

gst-tax-mcp

by zoeb-nomi

classify_hsn_sac

Classifies an HSN (goods) or SAC (services) code and returns the GST rate effective on a specified date, including rate history.

Instructions

Classify an HSN (goods) or SAC (services) code and return the GST rate in force on the given date (default today), with the rate history.

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": {
      "code": "<code>"
    },
    "name": "classify_hsn_sac"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
on_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two real behaviors: on_date defaults to today, and the response includes rate history rather than just the current rate. It says nothing about invalid/unknown codes, required code format or digit length, or whether the lookup is purely read-only, so meaningful gaps remain for an unannotated tool.

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?

A single front-loaded sentence with no filler; the code→rate→history order mirrors the call and return. The stray line break inside the sentence is the only blemish.

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

Completeness3/5

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

With no output schema and no annotations, the description does well to characterize the return (current rate plus history) and the date default. For a two-parameter lookup it still leaves the agent guessing on input format and failure modes, which is a moderate rather than complete gap.

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

Parameters3/5

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

Schema coverage is 0%, so the description must compensate, and it partially does: it explains that code accepts either an HSN (goods) or SAC (services) code and that on_date selects the rate date with today as default. It omits the expected code format (digit length, prefix rules) and the date string format, which are exactly the details missing from the bare `string` schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource pair ("classify an HSN (goods) or SAC (services) code") and states the deliverable (GST rate in force on a date, plus rate history). It implicitly separates itself from siblings like calc_gst_liability or gst_applicability by being a lookup/classification rather than a computation, though it never names an alternative.

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?

Usage is only implied: an agent can infer you call this when you have a code and need its GST rate. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling such as gst_applicability for the reverse direction (rate → codes).

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