Skip to main content
Glama

reference-data

by dev.usaref
OverviewDiscussionsAdmin

compute_vat

PAID ($0.02). VAT breakdown for an amount: net, tax and gross using the country's current statutory rate, including per-levy components where the rate is composite (e.g. Ghana VAT + NHIL + GETFund). mode=add treats the amount as net; mode=extract backs VAT out of a gross amount. Pass api_key if you have one; otherwise the response explains how to pay via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoadd = amount is net (default); extract = amount is gross
amountYesAmount in the country's own currency
api_keyNoAPI key
countryYesISO country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "ca",
-  "cr",
-  "do",
-  "gt",
-  "hn",
-  "mx",
-  "pa",
-  "sv",
-  "us"
-]New value: +[
+  "bs",
+  "ca",
+  "cr",
+  "do",
+  "gt",
+  "hn",
+  "mx",
+  "pa",
+  "sv",
+  "us"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "ca",
-  "mx",
-  "us"
-]New value: +[
+  "ca",
+  "cr",
+  "do",
+  "gt",
+  "hn",
+  "mx",
+  "pa",
+  "sv",
+  "us"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "ca",
-  "us"
-]New value: +[
+  "ca",
+  "mx",
+  "us"
+]
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Discloses the cost ($0.02), that rates are current statutory, and that composite rates are handled (e.g., Ghana). Also explains what happens without an api_key, providing transparency about payment.

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?

Three sentences, each providing key information: cost, purpose, mode options, and api_key guidance. Front-loaded with cost to set expectations. No wasted words.

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?

Given no output schema, the description explains the output components (net, tax, gross, and per-levy details). It covers cost and payment, but could mention error handling or rate update frequency.

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 100%, so baseline is 3. The description adds value by explaining the 'mode' parameter behavior (add vs extract) and the notion of composite rates tied to the 'country' parameter.

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 clearly states it computes VAT breakdown (net, tax, gross) for an amount using current statutory rates, including composite rates for countries like Ghana. It distinguishes itself from siblings like compute_income_tax by focusing on VAT.

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

Usage Guidelines4/5

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

Explicitly explains the two modes (add vs extract) and when to use each. Also mentions api_key usage. However, it does not explicitly contrast with sibling tools like compute_income_tax.

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

All reference-data 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