Skip to main content
Glama

FreeDailyPro Tools

by com.freedailypro.api
OverviewDiscussionsAdmin

converters_vat_gst

Read-onlyIdempotent

VAT and GST calculator with a country rate table

Input Schema

NameRequiredDescriptionDefault
amountYesThe amount, in any currency.
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.
amountIncludesTaxNotrue when amount already includes the tax (the tax is taken out of it).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one useful behavioral fact — that rates come from an internal country table, consistent with openWorldHint=false — but says nothing about what the calculation returns (tax amount, net, gross) or how unknown countries behave.

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?

A single short, front-loaded sentence with zero filler. It is efficient but borders on under-specification rather than tightness.

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?

For a 4-parameter calculator with no output schema, the description should say what is computed and returned and how it differs from calculate_sales_tax. Neither is present, leaving the agent to open the schema and guess at result shape.

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%, so amount, country, ratePct precedence and amountIncludesTax are all fully documented in the schema. The description adds no syntax, format or edge-case detail beyond restating that a country rate table exists; baseline 3 applies.

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?

"VAT and GST calculator" names a concrete computation and resource, and "with a country rate table" clarifies that rates are built in. It does not, however, distinguish itself from the close sibling calculate_sales_tax, so an agent must infer the split.

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 or when-not-to-use guidance and no named alternative. The obvious alternative, calculate_sales_tax, is never mentioned, leaving the choice between the two to inference.

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

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