Skip to main content
Glama

reference-data

by dev.asiaref

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

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It reveals the tool is paid (costs $0.02), explains authentication options, and describes the composite rate handling.

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?

The description is concise (two sentences) and efficient, covering the core function and key details without unnecessary wording.

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 the parameter count and lack of output schema, the description adequately covers the tool's purpose, modes, authentication, and geographic scope, though it does not describe the return format.

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%, and the description adds meaning beyond the schema by explaining the 'add' and 'extract' modes, clarifying that amount is in the country's currency, and providing context for the api_key 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 that the tool computes VAT breakdown (net, tax, gross) for a given amount and country, and distinguishes itself from sibling tools like compute_income_tax by specifying VAT-specific behavior and modes.

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?

It provides explicit guidance on using the api_key parameter, explains the two modes (add/extract), and implies when to use each. However, it does not explicitly mention when not to use the tool or alternative approaches.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct reference-data query: minimum wage check, income tax computation, VAT breakdown, working days, public holidays, series current/history/snapshot/catalog, and settlement date. There is no overlap; even get_series and get_series_history are explicitly separated as current vs. historical values.

Naming Consistency4/5

Most tools follow a clear verb_noun pattern (check_, compute_, count_, get_, list_). The one outlier is settlement_date, which is a noun phrase rather than verb_noun, but the deviation is minor and does not cause confusion.

Tool Count5/5

With 10 tools, the set is well-scoped for a reference-data server covering tax, labor, calendars, and settlement. Each tool serves a distinct purpose and none feel redundant or unnecessary.

Completeness4/5

The server provides strong coverage: discovery via list_series, current and historical series values, a bulk snapshot, and domain-specific computations for minimum wage, income tax, VAT, working days, holidays, and settlement dates. Minor gaps exist (e.g., no direct tool for social security contributions), but the core reference-data workflows are well supported.

Resources