Skip to main content
Glama
paulieb89

UK Business Tools - Ledgerhall

by paulieb89

Get VAT Rate for Commodity

law_hmrc_get_vat_rate
Read-onlyIdempotent

Look up the VAT rate for a named UK goods or services category, returning rate type, percentage, conditions, and the official GOV.UK source.

Instructions

USE THIS TOOL WHEN you know the UK VAT category name for a good or service and want its VAT treatment.

Exact named-category lookup, not a free-text VAT classifier or tax advice. The query must equal a category name, ignoring only case, spacing, hyphens and apostrophe style. Extra qualifying words are never discarded: 'pet food' is its own category, and 'baby food' is not 'food'.

A match returns rate (standard, reduced, zero or exempt), rate_percentage (None for exempt), conditions in notes, the GOV.UK source_url, and that entry's verified_on date.

An unresolved query returns no rate: matched_category, rate, rate_percentage and verified_on are all null, never a default. Its notes list the category names. AFTER an unresolved result, retry with a listed name or call hmrc_search_guidance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commodity_codeYesCommodity code or plain-English description. E.g. 'food', 'domestic fuel', 'software', 'financial services', 'new build residential'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rateNoVAT rate category, or None when no specific category was confidently matched. None here is NOT a stand-in for any real rate — it means the lookup did not resolve, not that the item is outside VAT's scope.
notesNoAny additional notes or conditions on this rate
source_urlYesGOV.UK/HMRC guidance page backing the matched entry; for an unresolved query, the general VAT rates page to consult instead
verified_onNoDate the matched entry was last checked against GOV.UK/HMRC guidance. None for an unresolved query, since no entry was matched. A data-currency signal only — see `effective_from` for the rate's own legal commencement date, when known.
commodity_codeYesCommodity code or description queried
effective_fromNoDate the represented VAT treatment is known, on researched evidence, to have taken legal effect. None when no such commencement date has been established for this entry — that is common and does NOT imply the rate is new, uncertain, or unmatched. For data currency (when this entry was last checked against GOV.UK/HMRC guidance) see `verified_on` instead — the two are deliberately independent.
rate_percentageNoRate charged on a taxable supply: 20.0 (standard), 5.0 (reduced), 0.0 (zero). None for an exempt supply, which is not taxed at any rate (exempt is not the same as 0%), and None when `rate` is None.
matched_categoryNoThe static lookup table category the query exactly named (e.g. 'hot food'), or None when the query is not a category name. `rate`/`rate_percentage` are None whenever this is None — see `notes`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive, so the description only needs to add non-safety behavior. It does this well: exact matching rules, normalization rules, the fact that extra words are never discarded, null-on-no-match behavior with no defaults, and the content of notes on failure.

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 front-loaded with the usage trigger and is organized into clear sections: when to use, matching rules, successful return values, and unresolved-result behavior. Every sentence earns its place; nothing is redundant or decorative.

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?

The description is complete for a one-parameter lookup tool. It covers success behavior, failure behavior, parameter constraints, and the fallback sibling tool. The output schema handles structured return details, and the description adds the semantic meaning an agent needs to interpret the response 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% and the schema already gives examples, but the description adds crucial semantics beyond it: the value must exactly equal a category name, not a free-text description or commodity code. It clarifies the potentially misleading 'commodity_code' property name and explains normalization and non-fuzzy matching in detail.

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's job: given a known UK VAT category name, return its VAT treatment. It explicitly distinguishes this from a free-text VAT classifier or tax advice, and names the sibling law_hmrc_search_guidance as the fallback, so an agent can tell them apart.

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 opening line is an explicit when-to-use trigger: use when you know the exact VAT category name. It also explains when not to use it (free-text queries, extra qualifying words) and tells the agent what to do after an unresolved result: retry with a listed name or call hmrc_search_guidance.

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