Skip to main content
Glama

reference-data

by dev.euroref
OverviewDiscussionsAdmin

compute_vat

PAID ($0.02). VAT breakdown for an amount: net, tax and gross using the country's current statutory rate, including per-levy components where the rate is composite (e.g. Ghana VAT + NHIL + GETFund). mode=add treats the amount as net; mode=extract backs VAT out of a gross amount. Pass api_key if you have one; otherwise the response explains how to pay via x402. Optional receipt (boolean, default false): on a paid success, include an Ed25519 answer receipt at no extra USDC. An answer receipt is not a series certified extract (GET /v1/certified/{country}/{series} is $0.25 and is not an MCP tool) and is not legal advice. Verify with verify_answer_receipt against /certified/public-key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoadd = amount is net (default); extract = amount is gross
amountYesAmount in the country's own currency
api_keyNoAPI key
countryYesISO country code
receiptNoDefault false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.25; that SKU is not an MCP tool).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / receipt
      Added value: +{
+  "default": false,
+  "description": "Default false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.25; that SKU is not an MCP tool).",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "bg",
-  "ch",
-  "cz",
-  "de",
-  "dk",
-  "ee",
-  "es",
-  "eu",
-  "fi",
-  "fr",
-  "gb",
-  "gr",
-  "hu",
-  "ie",
-  "is",
-  "it",
-  "lt",
-  "lv",
-  "nl",
-  "no",
-  "pl",
-  "pt",
-  "ro",
-  "rs",
-  "se",
-  "tr",
-  "ua"
-]New value: +[
+  "at",
+  "be",
+  "bg",
+  "ch",
+  "cy",
+  "cz",
+  "de",
+  "dk",
+  "ee",
+  "es",
+  "eu",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hr",
+  "hu",
+  "ie",
+  "is",
+  "it",
+  "lt",
+  "lu",
+  "lv",
+  "mt",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "rs",
+  "se",
+  "si",
+  "sk",
+  "tr",
+  "ua"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "bg",
-  "ch",
-  "cz",
-  "de",
-  "dk",
-  "es",
-  "eu",
-  "fi",
-  "fr",
-  "gb",
-  "gr",
-  "hu",
-  "ie",
-  "is",
-  "it",
-  "nl",
-  "no",
-  "pl",
-  "pt",
-  "ro",
-  "rs",
-  "se",
-  "tr",
-  "ua"
-]New value: +[
+  "at",
+  "be",
+  "bg",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "ee",
+  "es",
+  "eu",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hu",
+  "ie",
+  "is",
+  "it",
+  "lt",
+  "lv",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "rs",
+  "se",
+  "tr",
+  "ua"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "bg",
-  "ch",
-  "cz",
-  "de",
-  "dk",
-  "es",
-  "fi",
-  "fr",
-  "gb",
-  "gr",
-  "hu",
-  "ie",
-  "is",
-  "it",
-  "nl",
-  "no",
-  "pl",
-  "pt",
-  "ro",
-  "rs",
-  "se",
-  "tr",
-  "ua"
-]New value: +[
+  "at",
+  "be",
+  "bg",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "es",
+  "eu",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hu",
+  "ie",
+  "is",
+  "it",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "rs",
+  "se",
+  "tr",
+  "ua"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "ch",
-  "cz",
-  "de",
-  "dk",
-  "es",
-  "fi",
-  "fr",
-  "gb",
-  "gr",
-  "hu",
-  "ie",
-  "it",
-  "nl",
-  "no",
-  "pl",
-  "pt",
-  "ro",
-  "rs",
-  "se",
-  "tr"
-]New value: +[
+  "at",
+  "be",
+  "bg",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "es",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hu",
+  "ie",
+  "is",
+  "it",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "rs",
+  "se",
+  "tr",
+  "ua"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "ch",
-  "cz",
-  "de",
-  "dk",
-  "es",
-  "fi",
-  "fr",
-  "gb",
-  "gr",
-  "hu",
-  "ie",
-  "it",
-  "nl",
-  "no",
-  "pl",
-  "pt",
-  "ro",
-  "se",
-  "tr"
-]New value: +[
+  "at",
+  "be",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "es",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hu",
+  "ie",
+  "it",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "rs",
+  "se",
+  "tr"
+]
  7. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "de",
-  "dk",
-  "es",
-  "fr",
-  "gb",
-  "ie",
-  "it",
-  "nl",
-  "pl",
-  "se"
-]New value: +[
+  "at",
+  "be",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "es",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hu",
+  "ie",
+  "it",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "se",
+  "tr"
+]
  8. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "de",
-  "es",
-  "fr",
-  "gb",
-  "it",
-  "nl"
-]New value: +[
+  "at",
+  "be",
+  "de",
+  "dk",
+  "es",
+  "fr",
+  "gb",
+  "ie",
+  "it",
+  "nl",
+  "pl",
+  "se"
+]
  9. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the $0.02 fee, payment flow via x402, receipt behavior, and what the receipt is not (certified extract, legal advice). It lacks explicit error-condition or rate-limit details, but the critical behavioral traits are covered.

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 dense but every sentence adds value: cost, purpose, mode, api_key, receipt, verification, and legal disclaimers. It is slightly long due to the receipt caveats, but the structure is logical and front-loaded with the most critical info (PAID, VAT breakdown).

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 paid tool with no output schema, the description covers the essential invocation details: cost, payment, auth, mode behavior, receipt handling, and verification path. The return values (net, tax, gross) are stated, and edge-case caveats like composite rates are included. Nothing needed to call and understand the tool is missing.

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?

The schema already describes all parameters (100% coverage), so the baseline is 3. The description adds meaningful semantics beyond the schema by explaining mode=add/extract behavior, the composite rate example, and clarifying the receipt flag's implications. This pushes it above baseline.

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 computes a VAT breakdown (net, tax, gross) using the country's statutory rate, with specific mention of composite rates. It distinguishes itself from siblings like compute_income_tax and compute_employment_cost through the explicit VAT focus and mode handling.

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?

The description gives clear context on how to use the tool, including mode semantics (add vs extract), payment requirements, and optional receipt. It does not explicitly state when not to use it versus alternative tax tools, but the scope is unambiguous enough that an agent would not confuse it with siblings.

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

All reference-data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources