reference-data

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

Name	Required	Description
`mode`	No	add = amount is net (default); extract = amount is gross
`amount`	Yes	Amount in the country's own currency
`api_key`	No	API key
`country`	Yes	ISO country code

TDQS

A4.3/5.0

Behavior4/5

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

No annotations provided, but description discloses cost ($0.02), paywall via x402, and detailed output components. No contradictions. Sufficient transparency for a paid tool.

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 front-load key info (cost, purpose, modes) with no redundant text. Every sentence provides unique value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 parameters, full schema coverage, no output schema, and no annotations, description covers usage modes, payment, and country-specific composite rates. Fully sufficient for agent to decide and invoke.

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

Parameters3/5

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

Schema covers all 4 parameters with descriptions (100% coverage). Description adds value by clarifying mode default ('add' as net) and hinting at composite rate behavior, but does not significantly extend schema detail for other params.

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?

Description clearly states it computes VAT breakdown (net, tax, gross) with per-levy components for composite rates, and distinguishes between two modes (add/extract). Tool name 'compute_vat' is well-aligned with purpose.

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 when to use mode=add vs mode=extract, and notes payment process (api_key or x402). However, 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 tools Inspect

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.3/5.0

Disambiguation5/5

Each of the 11 tools addresses a clearly distinct operation: compliance checking, income tax, payroll, VAT, working days, holidays, series queries (current/history/snapshot/catalog), and settlement date. Even within the tax and calendar families, the descriptions precisely delineate boundaries, so there is no realistic risk of an agent selecting the wrong tool.

Naming Consistency4/5

The vast majority of tools follow a consistent verb_noun snake_case pattern (check_, compute_, get_, list_, count_). The only deviation is settlement_date, which is a noun phrase rather than verb_noun, but it is still clear and idiomatic. This single outlier prevents a perfect score.

Tool Count5/5

With 11 tools, the server is well-scoped for a reference-data domain covering statutory rates, calculations, calendars, and settlement conventions. Each tool has a distinct purpose and earns its place; the count is neither thin nor bloated.

Completeness4/5

The server provides strong coverage of its stated domain: statutory tax computations, payroll, minimum wage, VAT, holidays, working days, and settlement dates, plus a generic series API for extensibility. Minor gaps exist, such as payroll only supporting Nigeria and Kenya and no standalone social-security contributor, but the response descriptions explicitly disclose these limits, and the generic series endpoint provides a workaround for common lookups.

Resources

Need Help?