Skip to main content
Glama

reference-data

by dev.euroref

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.4/5.0
Behavior4/5

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

Without annotations, the description carries the full burden. It discloses the cost ($0.02), the behavior of modes, and the fallback for missing api_key. It does not cover error cases or rate limits, but these are less critical for a simple computation.

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 packs essential information. The cost note upfront is slightly abrupt but effective. Could be slightly more structured, but overall it is efficient.

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 reasonably explains the output (net, tax, gross) and includes composite rate details. It does not detail error handling, but for a VAT tool this is sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant value: explaining mode options beyond the enum, giving a concrete example of composite rates, and clarifying the api_key parameter's role in payment. This exceeds the baseline of 3.

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 an amount using the country's statutory rate, and mentions composite rates. It distinguishes itself from sibling tools like compute_income_tax by focusing on VAT. The 'PAID ($0.02)' note adds clarity about cost.

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 explains when to use 'add' vs 'extract' modes and what to do if no api_key is provided. It does not explicitly state when not to use this tool, but the context is clear enough for an agent to decide.

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.2/5.0
Disambiguation5/5

Each tool targets a distinct operation: minimum wage, income tax, VAT, working days, holidays, series data, and settlement dates. No overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., check_minimum_wage, compute_income_tax, get_public_holidays, list_series). Only 'settlement_date' is a noun phrase but still clear.

Tool Count5/5

10 tools cover a well-scoped domain of economic reference data without bloat. The count feels appropriate for the server's purpose.

Completeness4/5

Covers core areas: wage, tax, VAT, holidays, series, settlement dates. Minor gaps exist (e.g., no social security or currency data), but the scope is clearly defined and noted.

Resources