Skip to main content
Glama

reference-data

compute_vat

Read-onlyIdempotent

PAID ($0.01). 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 (instant card checkout at /pricing); otherwise the response explains how to pay via x402. The evaluation country is free to try (see list_series). 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.10 and is not an MCP tool) and is not legal advice. Verify with verify_answer_receipt against /certified/public-key.

Input 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.10; that SKU is not an MCP tool).

Output Schema

NameRequiredDescriptionDefault
netNo
taxNo
rateNo
basisNo
errorNoPresent on a free refusal or error; no charge
grossNo
statusNoAnswer status, e.g. computed or an honest no-answer status
countryNo
receiptNoEd25519 answer receipt when receipt=true on a paid success
questionNo
workingsNo
no_chargeNo
price_usdNo
disclaimerNo
how_to_payNo
provenanceNoCited official sources behind the answer
bind_seriesNo
explanationNo
label_basisNoInputs and the rule ids that produced the two labels
x_next_bindNo
http_endpointNo
coverage_labelNoHow much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules
confidence_labelNoEvidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules
payment_requiredNotrue when the call needs payment; how_to_pay explains x402 or card

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / receipt / description
      Previous value: -"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)."New value: +"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.10; that SKU is not an MCP tool)."
    • removedOutput schema / properties / label_basis / properties / source_type / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / label_basis / properties / source_type / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / label_basis / properties / verification_age_days / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / label_basis / properties / verification_age_days / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. Changed3 schema fields changed
    • addedOutput schema / properties / confidence_label
      Added value: +{
      +  "description": "Evidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules",
      +  "enum": [
      +    "high",
      +    "medium",
      +    "low"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / coverage_label
      Added value: +{
      +  "description": "How much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules",
      +  "enum": [
      +    "ready",
      +    "partial",
      +    "gap"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / label_basis
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Inputs and the rule ids that produced the two labels",
      +  "properties": {
      +    "confidence_reasons": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "coverage_reasons": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "inputs": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "rules": {
      +      "type": "string"
      +    },
      +    "rules_version": {
      +      "type": "string"
      +    },
      +    "source_type": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    },
      +    "verification_age_days": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "description": "VAT breakdown",
      +  "properties": {
      +    "basis": {},
      +    "bind_series": {},
      +    "country": {
      +      "type": "string"
      +    },
      +    "disclaimer": {},
      +    "error": {
      +      "description": "Present on a free refusal or error; no charge"
      +    },
      +    "explanation": {},
      +    "gross": {},
      +    "how_to_pay": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "http_endpoint": {
      +      "type": "string"
      +    },
      +    "net": {},
      +    "no_charge": {
      +      "type": "boolean"
      +    },
      +    "payment_required": {
      +      "description": "true when the call needs payment; how_to_pay explains x402 or card",
      +      "type": "boolean"
      +    },
      +    "price_usd": {
      +      "type": "number"
      +    },
      +    "provenance": {
      +      "description": "Cited official sources behind the answer"
      +    },
      +    "question": {},
      +    "rate": {},
      +    "receipt": {
      +      "description": "Ed25519 answer receipt when receipt=true on a paid success"
      +    },
      +    "status": {
      +      "description": "Answer status, e.g. computed or an honest no-answer status",
      +      "type": "string"
      +    },
      +    "tax": {},
      +    "workings": {},
      +    "x_next_bind": {}
      +  },
      +  "type": "object"
      +}
  4. 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"
      +}
  5. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "ae",
      -  "bd",
      -  "bh",
      -  "cn",
      -  "hk",
      -  "id",
      -  "il",
      -  "in",
      -  "jp",
      -  "kr",
      -  "kw",
      -  "kz",
      -  "lk",
      -  "my",
      -  "om",
      -  "ph",
      -  "pk",
      -  "qa",
      -  "sa",
      -  "sg",
      -  "th",
      -  "tr",
      -  "tw",
      -  "vn"
      -]New value: +[
      +  "ae",
      +  "bd",
      +  "bh",
      +  "cn",
      +  "hk",
      +  "id",
      +  "il",
      +  "in",
      +  "iq",
      +  "jo",
      +  "jp",
      +  "kr",
      +  "kw",
      +  "kz",
      +  "lk",
      +  "my",
      +  "np",
      +  "om",
      +  "ph",
      +  "pk",
      +  "qa",
      +  "sa",
      +  "sg",
      +  "th",
      +  "tr",
      +  "tw",
      +  "uz",
      +  "vn"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "ae",
      -  "bd",
      -  "bh",
      -  "cn",
      -  "hk",
      -  "id",
      -  "il",
      -  "in",
      -  "jp",
      -  "kr",
      -  "kw",
      -  "my",
      -  "om",
      -  "ph",
      -  "pk",
      -  "qa",
      -  "sa",
      -  "sg",
      -  "th",
      -  "tr",
      -  "tw",
      -  "vn"
      -]New value: +[
      +  "ae",
      +  "bd",
      +  "bh",
      +  "cn",
      +  "hk",
      +  "id",
      +  "il",
      +  "in",
      +  "jp",
      +  "kr",
      +  "kw",
      +  "kz",
      +  "lk",
      +  "my",
      +  "om",
      +  "ph",
      +  "pk",
      +  "qa",
      +  "sa",
      +  "sg",
      +  "th",
      +  "tr",
      +  "tw",
      +  "vn"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "ae",
      -  "bd",
      -  "cn",
      -  "hk",
      -  "id",
      -  "in",
      -  "jp",
      -  "kr",
      -  "my",
      -  "ph",
      -  "pk",
      -  "qa",
      -  "sa",
      -  "sg",
      -  "th",
      -  "tr",
      -  "tw",
      -  "vn"
      -]New value: +[
      +  "ae",
      +  "bd",
      +  "bh",
      +  "cn",
      +  "hk",
      +  "id",
      +  "il",
      +  "in",
      +  "jp",
      +  "kr",
      +  "kw",
      +  "my",
      +  "om",
      +  "ph",
      +  "pk",
      +  "qa",
      +  "sa",
      +  "sg",
      +  "th",
      +  "tr",
      +  "tw",
      +  "vn"
      +]
  8. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "bd",
      -  "id",
      -  "in",
      -  "jp",
      -  "kr",
      -  "my",
      -  "ph",
      -  "sg",
      -  "th",
      -  "vn"
      -]New value: +[
      +  "ae",
      +  "bd",
      +  "cn",
      +  "hk",
      +  "id",
      +  "in",
      +  "jp",
      +  "kr",
      +  "my",
      +  "ph",
      +  "pk",
      +  "qa",
      +  "sa",
      +  "sg",
      +  "th",
      +  "tr",
      +  "tw",
      +  "vn"
      +]
  9. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "in",
      -  "jp",
      -  "kr",
      -  "ph",
      -  "sg"
      -]New value: +[
      +  "bd",
      +  "id",
      +  "in",
      +  "jp",
      +  "kr",
      +  "my",
      +  "ph",
      +  "sg",
      +  "th",
      +  "vn"
      +]
  10. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the $0.01 cost, the x402 payment fallback, the receipt behavior (Ed25519, free on paid success, absent on 402/refusals), the 'not legal advice' caveat, and the verify_answer_receipt verification path. This is unusually rich behavioral context for an agent.

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?

Purpose and cost are front-loaded, and the sentences are information-dense. However the receipt behavior is explained both in the description and the schema's receipt description, which is mild redundancy in an otherwise tight definition.

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 an output schema present, return-value details are unnecessary, and the description already covers pricing, payment, receipt/verification and legal caveats. Nothing an agent needs in order to invoke this correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already documents mode (add/extract), amount currency, country ISO code and receipt. The description restates the mode semantics but adds no format detail beyond the schema, so the baseline 3 applies.

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+resource ('VAT breakdown for an amount: net, tax and gross') plus the exact output fields and the composite-rate case (Ghana VAT + NHIL + GETFund). This clearly separates it from siblings like compute_income_tax and compute_employment_cost, which handle different tax computations.

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?

Gives concrete operating context: pass api_key for instant checkout, otherwise x402 payment is explained in the response, and names the free evaluation country pointing to list_series. It does not explicitly contrast when to prefer this over sibling tax tools, but the usage conditions are otherwise clear.

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