Skip to main content
Glama

Avanciq - tax rates, codes, e-invoices, calculation checks

VAT / GST rate on a date

vat_rate
Read-onlyIdempotent

1 call. Official VAT/GST/sales-tax rate for a country (EU 27, UK, CH, NO, IN, JP, SG, NZ, AE, Canada provinces, 22 US states) on a given date, with valid-from/to, official source link, the date we read it and a receipt id. Use it instead of recalling rates from memory, especially around rate changes. Returns standard rate + reduced rates; it does not map products to reduced rates. Uncovered places answer status not_covered (never a guess).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>"
    },
    "name": "vat_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional: the date that matters (invoice/supply date) as YYYY-MM-DD. Default today.
regionNoOptional: Canadian province (ON, QC, BC, NS...) or US state (CA, TX, NY...). US answers are the state-level rate only, no local add-ons.
countryYesISO 3166 two-letter code, e.g. DE, FR, GB, IN, SG, CA, US. 'CA-QC' / 'US-TX' style also works.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description still adds real behavioral detail beyond that: the response includes valid-from/to, an official source link, a read date and a receipt id, and uncovered jurisdictions return status not_covered rather than a guessed rate. '1 call' hints at cost/latency but is left unexplained.

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 leading '1 call.' and the coverage enumeration are front-loaded, and the exclusion and not_covered fallback come last, which is a sensible order. The second sentence is a run-on that packs coverage, return fields and date semantics together, costing it a point on readability.

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?

With 3 simple parameters, full schema descriptions and no output schema, the description carries everything an agent needs: what it returns, what it refuses to do, coverage limits, and the uncovered-place fallback. No material gap remains.

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 coverage is 100%, so baseline is 3. The description adds value beyond the schema by enumerating the covered jurisdiction set, which tells the agent which country and region values will actually resolve and that Canadian provinces and US states are the intended region inputs.

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 states a specific verb and resource ('Official VAT/GST/sales-tax rate for a country on a given date') and then bounds the scope with an explicit jurisdiction list (EU 27, UK, CH, NO, IN, JP, SG, NZ, AE, Canadian provinces, 22 US states). It also draws a hard line against product-level rate mapping, which separates it from rate-lookup-adjacent siblings like verify_calculation.

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

Usage Guidelines4/5

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

It gives a clear positive trigger ('Use it instead of recalling rates from memory, especially around rate changes') and a negative boundary ('it does not map products to reduced rates'). It does not name a sibling tool to use for the excluded case, so an agent must infer the alternative, which keeps it short of a 5.

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