Skip to main content
Glama

list_tax_rates

Read-only

List statutory tax-rate slabs by jurisdiction — IN GST (5/12/18/28 + zero + exempt + composition trader/manufacturer/restaurant + compensation cess), UK VAT (20 / 5 / zero / exempt), AU GST (10 / GST-free / input-taxed), US sales-tax (state-administered summary, no federal rate), CA GST 5% + HST 13% ON / 15% Atlantic / 14% NS + provincial PST 7% BC / 6% SK / RST 7% MB + QST 9.975% QC, SG GST 9% (+ superseded 8% / zero / exempt), NZ GST 15% (+ zero / exempt), AE VAT 5% (+ zero / exempt). Filter by country, taxType (GST/VAT/Sales-Tax/HST/PST/QST/IGST/CGST-SGST/TDS/TCS), or scheme (standard / reduced / zero / exempt / input-taxed / composition / cess / state-summary). Every entry carries an effective-from date and an authoritative source URL (CBIC, gov.uk, ATO, CRA, IRAS, IRD, FTA, Tax Foundation) — agents should confirm the rate against the source before quoting figures to a user. Use this when a user asks "what is the GST rate on X?", "what VAT band does Y fall into?", or "what are the composition slabs in India?". This is the public statutory reference — for an org-specific tax assignment use the authenticated books_classify_event tool.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tax_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
schemeNoFilter by slab category — standard, reduced, zero, exempt, input-taxed, composition, cess.
countryNoFilter to one jurisdiction. Omit to return every supported country.
taxTypeNoFilter by statutory tax type (GST, VAT, Sales-Tax, HST, PST, QST, etc.).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / scheme / description
      Previous value: -"Filter by slab category — standard, reduced, zero, exempt, composition, cess."New value: +"Filter by slab category — standard, reduced, zero, exempt, input-taxed, composition, cess."
    • changedInput schema / properties / scheme / enum
      Previous value: -[
      -  "standard",
      -  "reduced",
      -  "zero",
      -  "exempt",
      -  "composition",
      -  "cess",
      -  "state-summary"
      -]New value: +[
      +  "standard",
      +  "reduced",
      +  "zero",
      +  "exempt",
      +  "input-taxed",
      +  "composition",
      +  "cess",
      +  "state-summary"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / taxType / description
      Previous value: -"Filter by statutory tax type (GST, VAT, Sales-Tax, HST, etc.)."New value: +"Filter by statutory tax type (GST, VAT, Sales-Tax, HST, PST, QST, etc.)."
    • changedInput schema / properties / taxType / enum
      Previous value: -[
      -  "GST",
      -  "IGST",
      -  "CGST-SGST",
      -  "VAT",
      -  "Sales-Tax",
      -  "HST",
      -  "TDS",
      -  "TCS"
      -]New value: +[
      +  "GST",
      +  "IGST",
      +  "CGST-SGST",
      +  "VAT",
      +  "Sales-Tax",
      +  "HST",
      +  "PST",
      +  "QST",
      +  "TDS",
      +  "TCS"
      +]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description stays consistent with a static public reference. It adds genuinely non-obvious behavior: every entry carries an effective-from date and an authoritative source URL, and agents are told to verify against the source before quoting figures — a real usage constraint beyond the annotations. It stops short of describing result volume, ordering, or whether superseded rates (e.g. Singapore's 8%) are returned alongside current ones.

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

Conciseness3/5

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

The purpose, the triggering questions, and the sibling boundary are front-loaded and earn their place. However, the enormous parenthetical cataloguing every country's rate slabs is dense, partially duplicates what the tool returns, and risks carrying stale figures in prose. The core message would survive with the rate enumeration trimmed.

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?

There is no output schema, so the description must cover return content, and it does: entries include an effective-from date and an authoritative source URL. Combined with coverage of all eight jurisdictions, all filter axes, and the boundary against the org-specific classifier tool, an agent has everything needed to call it and interpret results responsibly.

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 description coverage is 100% and all three parameters are enums with documented values, so the schema already carries the filter semantics. The description restates the same three filter axes and elaborates the enum members, adding scoping detail ("omit country to return every supported country" is echoed from the schema) but little that is new. Baseline 3 applies when the schema does the heavy lifting.

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?

Opens with a specific verb and resource — "List statutory tax-rate slabs by jurisdiction" — then spells out the exact jurisdictions and rate bands covered, so an agent knows the scope without opening the schema. It also draws a boundary against the authenticated books_classify_event tool, which handles org-specific tax assignment.

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

Usage Guidelines5/5

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

Gives explicit triggering questions ("what is the GST rate on X?", "what VAT band does Y fall into?", "what are the composition slabs in India?") and names the alternative tool plus the condition that selects it (org-specific assignment → books_classify_event). The when-to-use and when-not-to-use are both stated rather than inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources