Skip to main content
Glama

reference-data

by dev.mearef

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?

With no annotations, the description carries the full burden. It discloses the paid nature ($0.02), the two modes of operation, and composite rate handling. It does not detail error handling or rate limits, but the core behavior is transparent.

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?

The description is three sentences, each serving a distinct purpose: function overview, mode explanation, and payment info. No wasted words; front-loaded with the main purpose.

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 tool's complexity (VAT with composite rates, paid), the description covers essential aspects: modes, payment, and country-specific behavior. No output schema is provided, but the description implies the result structure. A brief note on response format would improve completeness, but it's already substantial.

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 'add' vs 'extract' mode semantics, the api_key role, and the composite rate nuance for certain countries. It supplements the schema without redundancy.

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's purpose: computing VAT breakdown (net, tax, gross) using the country's statutory rate, including composite levies. It distinguishes from sibling tools like 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?

The description explains when to use 'add' vs 'extract' modes and mentions the api_key for paid users. It does not explicitly state when not to use the tool, but the context (paid tool, specific VAT calculation) is clear enough.

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 (check, compute, count, get, list) and a distinct resource (minimum wage, income tax, VAT, working days, holidays, series, settlement). The series tools are clearly differentiated by granularity (list, current, history, snapshot), and compute/check tools apply calculations rather than just returning values.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (check_, compute_, count_, get_, list_), but settlement_date is a noun phrase without a verb, and the verbs vary (check, compute, count, get, list) rather than using a single style. Still, the names are descriptive and predictable.

Tool Count5/5

10 tools is within the ideal 3-15 range, and each tool earns its place by covering a distinct facet of statutory reference data: taxes, compliance checks, calendars, series, and settlement. There is no bloat or sense of missing essential tools.

Completeness4/5

The surface provides strong coverage: compliance checks (minimum wage, taxes), calendar operations (holidays, working days), series catalog/current/history/snapshot, and settlement dates. Minor gaps include no direct tool for settlement conventions (mentioned only as an external endpoint) and no standalone tax bracket getter, but get_series likely covers some rates and users can infer brackets from compute_income_tax.

Resources