Skip to main content
Glama

reference-data

by dev.latamref

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

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

No annotations exist, so description fully bears the burden. It discloses the cost ($0.02), reliance on current statutory rates, composite rate handling (e.g., Ghana VAT+NHIL+GETFund), and behavior without api_key (explains x402 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?

Single, dense paragraph with no redundant words. Front-loaded with key action and resource, then details. Every sentence earns its place.

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 what is computed (net, tax, gross) and composite rate details. However, it does not specify the return format or structure, which could be helpful for an agent to parse results.

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 already covers all 4 parameters (100% coverage). Description adds critical nuance: mode=add treats amount as net, mode=extract backs VAT out of gross, and api_key is optional with fallback explanation. Enhances understanding beyond schema.

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 the tool computes VAT breakdown (net, tax, gross) using current statutory rates, including composite rates. It distinguishes from siblings (e.g., compute_income_tax) by focusing specifically 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?

It explains when to use mode=add vs mode=extract and mentions api_key fallback. However, it does not explicitly state when not to use this tool or compare to siblings, though sibling names are distinct.

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

Each tool targets a distinct operation: compliance check, tax computation, VAT breakdown, day counting, holiday retrieval, series value/history/snapshot, catalog listing, and settlement date calculation. Even where underlying data overlaps (e.g., minimum wage as a series), the outputs and use cases are clearly differentiated.

Naming Consistency4/5

Nine of ten tools follow a clear verb_noun pattern (check_minimum_wage, compute_income_tax, compute_vat, count_working_days, get_public_holidays, get_series, get_series_history, get_snapshot, list_series). The outlier is settlement_date, which uses a noun phrase rather than a verb-based name, though it remains unambiguous and readable.

Tool Count5/5

With 10 tools, the server is well-scoped for its reference-data purpose, covering tax, wages, holidays, working days, series discovery, and settlement dates. Each tool earns its place without redundancy or bloat.

Completeness5/5

The surface provides comprehensive coverage: discovery via list_series, current/historical data via get_series and get_series_history, a full snapshot, tax computations, wage compliance, public holidays, working day counts, and settlement date calculations. There are no obvious gaps or dead ends for the intended domain.

Resources