Skip to main content
Glama
Meru-Fin-Tech

HelloBooks AI MCP Server

by Meru-Fin-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_tax_rates

List statutory tax rate slabs for GST, VAT, and sales tax across jurisdictions. Filter by country, tax type, or scheme to find applicable rates with official source URLs.

Instructions

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), US sales-tax (state-administered summary, no federal rate), CA GST 5% + HST 13% ON / 15% Atlantic, SG GST 9%, NZ GST 15%, AE VAT 5%. Filter by country, taxType (GST/VAT/Sales-Tax/HST/IGST/CGST-SGST/TDS/TCS), or scheme (standard / reduced / zero / exempt / 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.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.0

TDQS

A4.8/5.0
Behavior5/5

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

No annotations provided, so the description carries full burden. It discloses key behaviors: each entry has an `effective_from` date and `source` URL, advises confirming with source before quoting, and clarifies this is a public statutory reference vs. org-specific tool. This is thorough and honest.

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?

The description is lengthy but well-structured: opening with jurisdiction examples, then filtering options, then usage guidance. Every sentence adds value, though some could be slightly more concise. It's organized for quick scanning.

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?

Despite no output schema, the description explains what the response contains (effective-from date, source URL) and provides comprehensive coverage of supported countries, tax types, and schemes. It also gives guidance on confirming sources, making it complete for the tool's purpose.

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 description coverage is 100%, but the description adds significant context beyond schema enums by listing example countries and tax types, and explaining the meaning of `scheme` values (e.g., composition, cess). This helps the agent understand parameter semantics beyond just the enum values.

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?

The description clearly states the tool lists statutory tax-rate slabs by jurisdiction, provides concrete examples of rates and countries, and distinguishes from sibling tools like `lookup_tax_rate`. The verb 'list' and resource 'tax-rate slabs' is specific and informative.

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?

Explicit usage guidance: use when a user asks specific tax rate questions (e.g., 'what is the GST rate on X?'), and contrast with an alternative tool for org-specific tax assignment. This effectively helps the agent decide when to invoke this tool.

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

Deploy Server

Other Tools