Skip to main content
Glama

HelloBooks AI Agents MCP Server

lookup_tax_rate

Read-only

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.

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": "lookup_tax_rate"
  }
}

Input 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".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description is consistent with that, adding that this is public statutory reference with no customer data. It goes beyond the annotations by disclosing the fuzzy best-match behavior and the returned fields (matched rate, match score, authoritative source URL), which matters because a fuzzy match can silently return an approximate answer. It does not discuss tie-breaking or what happens when the fuzzy match finds nothing, which keeps it short of a 5.

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?

Front-loaded with the core action and the two modes, followed by return values, usage triggers, and sibling routing in a logical order. It is somewhat dense in a single run-on first sentence, and the inline id/category examples partially duplicate the schema's own examples, but nothing is filler.

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?

For a 3-parameter read-only lookup with no output schema, the description covers modes of invocation, what is returned (rate, match score, source), when to use it versus the sibling list tool, and the data-scope guarantee. An agent has everything needed to choose a mode and call it correctly.

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%, so the baseline would be 3, but the description adds real meaning beyond the schema: `id` is framed as a deterministic lookup while `country` + `category` is a fuzzy best-match, a semantic distinction the schema does not state. The sample categories ("office supplies", "restaurant", "exports", "domestic fuel") also signal the expected free-text granularity.

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 and resource — pick a single statutory tax-rate slab — and immediately splits it into two named modes (exact `id` lookup vs. `country` + free-text `category` fuzzy match), with concrete id examples. It also names the sibling it is not (list_tax_rates), so an agent can distinguish it without opening either schema.

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 when-to-use triggers in the form of sample user questions ("what slab does X fall into in India?") and an explicit exclusion routing to list_tax_rates for broader exploration. The deterministic-vs-fuzzy choice between the two input modes is spelled out rather than left to inference.

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.