Skip to main content
Glama

Calculate South African VAT

sa_vat_calculate
Read-onlyIdempotent

Split a VAT-inclusive amount into VAT and the exclusive price, or add VAT to an exclusive amount, at the South African VAT rate in force on the date (15% since 1 April 2018). One amount or a list of lines, with per-line and total figures.

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

Input Schema

NameRequiredDescriptionDefault
dateNoSupply date YYYY-MM-DD (default today) — picks the rate from the rate history
linesNoSeveral lines instead of amount
amountNoOne amount in rand
inclusiveNotrue = amount(s) include VAT (default); false = amount(s) exclude VAT

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / lines / items / properties / amount / description
      Added value: +"Amount in rand for one unit"
    • addedInput schema / properties / lines / items / properties / description / description
      Added value: +"What the line is (shown back in the result)"
    • addedInput schema / properties / lines / items / properties / inclusive / description
      Added value: +"true = this line includes VAT; default is the top-level inclusive setting"
    • addedInput schema / properties / lines / items / properties / quantity / description
      Added value: +"Number of units (default 1)"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the description focuses on useful calculation semantics: historical rate selection and support for one amount or multiple lines with per-line and total figures. It adds meaningful behavior beyond the annotations, though it does not fully describe output shape or rounding.

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?

Two tightly written sentences front-load the core operation and then add rate-history context. There is no filler or repetition.

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 calculator with rich schema coverage and annotations that cover safety, the description gives enough operational context: inclusive versus exclusive handling, date-based rates, batch lines, and per-line/total output. Minor gaps remain around exact return values and rounding, but nothing critical for invoking the tool 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 coverage is 100%, so the schema already documents date, amount, inclusive, and lines. The description reinforces the one-amount-versus-lines usage and the date-based rate history, but it does not add detail about the vat enum, quantity, or inclusive overrides beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific operation: splitting VAT-inclusive amounts or adding VAT to exclusive amounts for South African VAT, including the rate-in-force date logic. It is clear and distinguishable from a classification tool, though it does not explicitly name alternatives such as sa_vat_classify.

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

Usage Guidelines3/5

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

The two calculation modes are described, which implies when the tool is useful, and the date-based rate selection gives useful context. However, there is no explicit when-to-use guidance versus siblings or any stated exclusions.

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.