Skip to main content
Glama

Calculate UAE VAT

calculate_vat
Read-onlyIdempotent

Use this when the user asks to add UAE VAT to an amount, how much VAT is inside a VAT-inclusive price, or what the VAT is on a reverse-charge supply ("add VAT to 12,500", "how much VAT is in 1,050 AED"). Works out UAE VAT (5%) for one or more amounts. By default amounts are net and VAT is added. Set amounts_include_vat when the amounts already include VAT, to extract it. Set reverse_charge for a supply where the recipient accounts for the VAT (no VAT on the invoice; the result says how much VAT the recipient self-accounts). Each line can be standard (5%), zero, exempt or out_of_scope; lines are rounded to 2 decimals first and the totals are the sum of the lines. Do not use it for whether a supply is zero-rated or exempt (check_vat_on_supply) or for VAT figures from the user's own records (get_vat_summary).

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

Input Schema

NameRequiredDescriptionDefault
linesNo
amountNoA single amount. Use lines instead for several amounts.
reverse_chargeNotrue for a reverse-charge supply.
amounts_include_vatNotrue when the amounts already include VAT.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), yet the description adds real behavior: amounts default to net, lines are rounded to 2 decimals before totals are summed, and reverse-charge results report what the recipient self-accounts rather than invoicing VAT. The main thing it leaves out is what the computed result object actually contains (per-line vs total figures), which matters for a calculator with no output schema.

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 when-to-use triggers and examples, then defaults, then modes, then exclusions, which is a sound order. The quoted example amounts partially duplicate the surrounding prose, so a sentence or two could be trimmed without losing signal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only calculator with an output-shape gap, the description is nearly complete: it covers mode selection, defaults, rounding, line types, and routing away from siblings. The missing piece is any indication of the return payload (line breakdown, VAT amount, totals), which the agent must infer since no output schema exists.

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 75% and the description adds semantics beyond it: the default net treatment of amounts, the effect of amounts_include_vat (extract rather than add), the reverse_charge consequence, and the four vat_type line categories with their rounding implication. It doesn't address the mutual exclusivity of amount vs lines, which the schema handles only in the lines field's own text.

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 opens with a concrete verb plus resource ("add UAE VAT to an amount") and explicit query types, including natural-language examples ("add VAT to 12,500", "how much VAT is in 1,050 AED"). It also names what the tool is not for, citing check_vat_on_supply and get_vat_summary, which makes it distinguishable from siblings without opening any other 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?

It gives explicit when-to-use triggers (adding VAT, VAT inside an inclusive price, reverse-charge VAT), concrete example phrasings, and explicit when-not-to-use cases that point to the correct alternative tools. It also states which flags to set for the inclusive-price and reverse-charge variants, so the agent knows which mode to select.

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