Skip to main content
Glama
Meru-Fin-Tech

HelloBooks AI MCP Server

lookup_tax_rate

Look up statutory tax rate slabs by exact ID or by country and category. Returns matched rate, score, and official source URL.

Instructions

Pick a single statutory tax-rate slab — either by exact id (e.g. IN-standard-18, GB-zero-0, CA-hst-13-on) for a deterministic lookup, or by country + free-text category (e.g. "office supplies", "restaurant", "exports", "domestic fuel") for a fuzzy best-match. Returns the matched rate, the match score, and the authoritative source URL. Use this when a user asks "what slab does X fall into in India?" or "what VAT rate applies to children's car seats?". For broader exploration (all slabs in a country / all rates of one scheme), use list_tax_rates. No customer data — public statutory reference only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoExact rate id, e.g. ``IN-standard-18`` or ``GB-zero-0``. When set, country/category are ignored.
countryNoCountry to search within. Required when ``id`` is not provided.
categoryNoFree-text query — "office supplies", "restaurant", "exports", "domestic fuel".
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns matched rate, match score, and source URL, and states it is a public statutory reference with no customer data. It does not detail match algorithm or failure modes, but is sufficient for a read-only lookup.

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?

The description is concise, well-structured, and front-loaded with action and scope. Every sentence adds value, includes examples, and provides guidance without fluff.

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?

Given no output schema and simple lookup nature, the description covers purpose, parameter behavior, output elements (rate, score, source), and distinguishes from sibling tool. It is complete and leaves no significant gaps.

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

Parameters5/5

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

Schema coverage is 100%, baseline 3. The description adds significant meaning beyond the schema by explaining the exact vs fuzzy mode, id override behavior, providing concrete examples of id formats and category queries, and tying parameters to use cases.

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 does a single lookup of a statutory tax rate slab, with two modes (exact by id or fuzzy by country+category). It distinguishes from the sibling tool list_tax_rates for broader exploration, using specific verbs like 'pick' and 'lookup'.

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?

The description explicitly provides when to use this tool (specific queries like 'what slab does X fall into?') and when not to ('For broader exploration... use list_tax_rates instead'). It includes example queries and clarifies that no customer data is involved.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Meru-Fin-Tech/HelloBooks-MCP-Public'

If you have feedback or need assistance with the MCP directory API, please join our Discord server