Skip to main content
Glama

EU VAT Calculator API - net/gross with each country's rate

eu_vat_calculator
Read-onlyIdempotent

Add or remove VAT for 30 European countries using their standard and reduced rates (or your own rate): net, VAT and gross amounts. Rates are built in, no outside call. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/eu-vat-calculator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "amount": 100,
      "country": "DE",
      "amountIs": "net"
    },
    "name": "eu_vat_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNostd, red1 or red2std
amountNoAmount
countryNoCountry code, e.g. DE, FR, BGDE
amountIsNonet (without VAT) or gross (with VAT)net
customRateNoYour own VAT rate in percent (overrides rate)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description adds genuinely useful behaviour beyond that: rates are built in with no external lookup, processing is server-side, files are deleted and nothing is stored. The 'files are deleted' claim is slightly incongruous for a pure calculation tool and no rounding/precision behaviour is described, keeping it short of a 5.

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 capability, then behaviour guarantees, then commercial terms — a sensible order with no filler sentences. The final pricing sentence is dense with a URL and currency detail but is legitimately actionable for the agent.

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 five optional, fully documented parameters and no output schema, the description names the returned quantities (net, VAT, gross) so an agent knows what to expect. Missing only minor specifics such as rounding rules or whether reduced rates depend on goods category.

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% with enum values on rate, country and amountIs, so the schema already carries parameter meaning and the baseline is 3. The description echoes that structure ('standard and reduced rates (or your own rate)', 'net, VAT and gross amounts') without adding format or precedence detail — notably it does not restate that customRate overrides rate.

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 and resource: 'Add or remove VAT for 30 European countries', and enumerates the outputs (net, VAT, gross amounts). This is unambiguously distinct from the arithmetic siblings (loan_calculator, percentage_calculator) because it is scoped to EU VAT rates by country.

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?

Usage is implied by the domain rather than stated: an agent infers it should be used when net/gross VAT conversion for a European country is needed. There is no explicit when-not guidance or comparison to an alternative, and the only conditional text is about pricing tiers (25 free calls/day, then $0.001 via x402), which is access policy rather than task routing.

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