Skip to main content
Glama

Vietnam Payroll and Tax Calculator

Personal income tax by bracket (Vietnam)

pit_only
Read-onlyIdempotent

Calculate Vietnamese personal income tax on a monthly taxable income that is already known (salary after compulsory insurance and family deductions), with the amount and tax of each bracket of the 5-bracket scale (5%, 10%, 20%, 30%, 35%; thresholds 10, 30, 60, 100 million VND). For non-residents: flat 20% of the income. Use gross_to_net instead when you start from a gross salary. Examples: {"taxable_income":24500000}; {"taxable_income":80000000,"as_of":"2026-03"}; {"taxable_income":50000000,"residency":"non_resident"}.

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": {
      "taxable_income": "<taxable_income>"
    },
    "name": "pit_only"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoSynonym of as_of (same formats: YYYY-MM or YYYY-MM-DD). Pass only one of as_of, month, date.
as_ofNoDate of the calculation: 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.
residencyNoTax residency: "resident" (default; progressive scale with deductions) or "non_resident" (flat 20% of gross, no deductions).
taxable_incomeYesMonthly taxable income in VND: for residents, salary after compulsory insurance and family deductions; for non-residents, the gross salary.

Output Schema

NameRequiredDescriptionDefault
taxYes
as_ofYes
notesYes
methodYes
sourcesYes
disclaimerYes
data_versionYes
taxable_incomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered; the description adds the computational behavior (progressive bracket rates and thresholds, flat 20% for non-residents) that the annotations cannot convey. It stops short of noting rounding/precision behavior or what the response contains, but that is minor given the output schema.

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 purpose and the sibling routing before the bracket detail, and the examples are compact and non-redundant. It is dense in one sentence (the bracket list with thresholds and rates), which reads a bit like a reference table, but every element is actionable and nothing is filler.

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?

For a pure calculation tool with one required input, an output schema already present, and full annotation coverage, the description supplies everything needed to call it correctly: input definition, residency branch, the tax rules applied, and the alternative tool to use instead. No meaningful gap remains for an agent to guess at.

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 value by pinning down what taxable_income must mean (post-insurance, post-deduction, or gross for non-residents) and by giving three concrete argument examples that demonstrate valid parameter combinations, including as_of and residency. The as_of/month/date synonym family is left to the schema, which already handles it well.

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 Vietnamese personal income tax) plus the exact scope: a monthly taxable income already net of insurance and family deductions, with the 5-bracket scale and thresholds spelled out. It also names the sibling it is not (gross_to_net), so an agent can separate it from the gross-salary path 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use is given ('monthly taxable income that is already known') and an explicit alternative with the switching condition ('Use gross_to_net instead when you start from a gross salary'). It also states the non-resident branch rule (flat 20%), which is the main branch an agent must get right.

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.