Skip to main content
Glama
Sign In

FreeDailyPro Calculators

by com.freedailypro.api
OverviewDiscussionsAdmin

converters_vat_gst

Read-onlyIdempotent

VAT and GST calculator with a country rate table

Input Schema

NameRequiredDescriptionDefault
linesNoInvoice lines at different rates: returns a subtotal per rate (byRate) and a grand total. Use instead of amount.
amountNoThe amount, in any currency. Send this, or vatAmount, or lines.
countryNoCountry name (for example Germany, United Kingdom, Australia, Singapore, UAE). Looks up the standard VAT/GST rate. Canada has one entry per province group, e.g. 'Canada - Ontario HST'. The error for an unknown name lists every supported entry.
ratePctNoVAT/GST rate in percent. Required unless country is sent. Takes priority over country.
vatAmountNoThe VAT amount shown on a receipt: returns the net and gross it implies at the rate (needs a rate above 0). Use instead of amount.
amountIncludesTaxNotrue when amount already includes the tax (the tax is taken out of it).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / amount / description
      Previous value: -"The amount, in any currency."New value: +"The amount, in any currency. Send this, or vatAmount, or lines."
    • addedInput schema / properties / lines
      Added value: +{
+  "description": "Invoice lines at different rates: returns a subtotal per rate (byRate) and a grand total. Use instead of amount.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "amount": {
+        "description": "The line amount (net, or gross when amountIncludesTax is true).",
+        "minimum": 0,
+        "type": "number"
+      },
+      "ratePct": {
+        "description": "This line's rate in percent. Defaults to the top-level ratePct or the country's standard rate.",
+        "minimum": 0,
+        "type": "number"
+      }
+    },
+    "required": [
+      "amount"
+    ],
+    "type": "object"
+  },
+  "maxItems": 200,
+  "type": "array"
+}
    • addedInput schema / properties / vatAmount
      Added value: +{
+  "description": "The VAT amount shown on a receipt: returns the net and gross it implies at the rate (needs a rate above 0). Use instead of amount.",
+  "minimum": 0,
+  "type": "number"
+}
    • removedInput schema / required
      Removed value: -[
-  "amount"
-]
  2. Changed5 schema fields changed
    • addedInput schema / properties / amount / description
      Added value: +"The amount, in any currency."
    • addedInput schema / properties / amountIncludesTax / description
      Added value: +"true when amount already includes the tax (the tax is taken out of it)."
    • addedInput schema / properties / country
      Added value: +{
+  "description": "Country name (for example Germany, United Kingdom, Australia, Singapore, UAE). Looks up the standard VAT/GST rate. Canada has one entry per province group, e.g. 'Canada - Ontario HST'. The error for an unknown name lists every supported entry.",
+  "type": "string"
+}
    • addedInput schema / properties / ratePct / description
      Added value: +"VAT/GST rate in percent. Required unless country is sent. Takes priority over country."
    • changedInput schema / required
      Previous value: -[
-  "amount",
-  "ratePct"
-]New value: +[
+  "amount"
+]
  3. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only 'with a country rate table', which conveys almost nothing beyond that—it doesn't mention that unknown country names throw an error listing supported entries, or that ratePct overrides country.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short phrase, so nothing is wasted, but it is under-specified rather than concise—more of a tagline than a usable definition for a 6-parameter calculator.

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

Completeness2/5

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

With no output schema, the description would be the only place to explain return shape (per-rate subtotals, net/gross derivation for vatAmount), and it says nothing. The rich schema compensates on inputs, but the overall definition is too thin for a multi-mode calculator.

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 every parameter carries a detailed description (including mutual exclusivity of amount / vatAmount / lines and the ratePct priority rule). The prose description adds no parameter meaning at all, so the baseline 3 for fully-documented schemas applies.

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

Purpose3/5

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

The description names the resource ('VAT and GST calculator') and adds a qualifier about a country rate table, so the basic function is inferable. However, it never distinguishes this from the close sibling calculate_sales_tax (or converters_state_tax), leaving an agent unsure which calculator to pick for a given tax computation.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as calculate_sales_tax. The agent gets no routing help beyond the tool name itself.

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

All FreeDailyPro Calculators 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