Skip to main content
Glama

Vietnam Payroll and Tax Calculator

10% tax withholding without a labour contract (Vietnam)

withholding_10pct
Read-onlyIdempotent

Calculate the 10% personal income tax an organisation withholds from a payment to a resident individual without a labour contract or with a contract under 3 months (freelance, service fees). Threshold per payment: 2 million VND before 1 July 2026, 5 million VND from that date (the effective date of Decree 253/2026/ND-CP); below it nothing is withheld. Caveat on the date: the decree also applies its provisions on residents' salary income to the whole tax year 2026, so the 5 million threshold may be read as applying from 1 January 2026; this is not confirmed, and for January-June 2026 the tool uses 2 million and says so in the notes. Notes cover the commitment-form exemption. Examples: {"amount":8000000}; {"amount":3000000,"as_of":"2026-03-15"}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "amount": "<amount>"
    },
    "name": "withholding_10pct"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoSynonym of as_of (same formats: YYYY-MM or YYYY-MM-DD). Pass only one of as_of, month, date.
as_ofNoPayment date: YYYY-MM (first day of that month) or YYYY-MM-DD. Default: today in Vietnam. Supported from 2026-01; earlier dates are rejected.
monthNoSynonym of as_of (same formats: YYYY-MM or YYYY-MM-DD). Pass only one of as_of, month, date.
amountYesAmount of one payment in VND (before tax) to a resident without a labour contract or with a contract under 3 months.

Output Schema

NameRequiredDescriptionDefault
as_ofYes
notesYes
amountYes
appliesYes
sourcesYes
paid_outYes
withheldYes
disclaimerYes
data_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes well beyond them: it discloses the threshold logic, the date-dependent rule switch, the unresolved legal reading of Decree 253/2026/ND-CP, and that the commitment-form exemption is surfaced in the notes. That is exactly the kind of domain caveat an agent cannot recover from structured fields.

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?

Front-loaded with the core rule, then the threshold, then the caveat, then examples — a logical order with no filler. The caveat sentence is long and nests several clauses, which slightly costs readability, but every sentence carries substantive information.

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?

Output schema exists, so return values need not be explained, and annotations plus the description cover behavior, thresholds, and the notes. The only gap is the lack of pointers to sibling tools for adjacent cases (salary income, net/gross conversion), which would complete the routing picture for a small calculator in a large family.

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 the baseline is 3, but the description adds real meaning the schema cannot: the date parameter changes which threshold applies (2M vs 5M VND), and the worked examples show how amount and as_of combine in practice. It also flags the legal ambiguity of applying the 5M threshold retroactively to January–June 2026.

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?

States a specific verb and resource — 'Calculate the 10% personal income tax an organisation withholds' — and immediately qualifies the population it applies to (resident individuals without a labour contract or with a contract under 3 months). An agent can distinguish this from salary-based tools like pit_only or gross_to_net without opening the schema.

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 applicability conditions are explicit and operational: no labour contract or contract under 3 months, freelance/service fees, and the per-payment threshold below which nothing is withheld. What is missing is routing guidance — it never names a sibling (e.g. pit_only or gross_to_net) for the labour-contract case, so the agent must infer the boundary itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.