Skip to main content
Glama

Vietnam Payroll and Tax Calculator

Employer cost of a salary (Vietnam)

employer_cost
Read-onlyIdempotent

Calculate what a monthly gross salary costs an employer in Vietnam: social insurance (sickness and maternity 3%, retirement 14%, occupational accident 0.5%), health insurance 3%, unemployment insurance 1% (not for foreigners), the 2% trade union fund, and the total cost; the employee's net pay is included. Options: as_of (YYYY-MM or YYYY-MM-DD, default today; month and date are accepted as synonyms), region I-IV or 1-4 (default I), dependents (residents only), residency resident|non_resident, nationality vietnamese|foreigner (foreigner = contract of 12 months or more: no unemployment insurance), insurance_base (if the insured salary differs from gross; not below the regional minimum), union_member (0.5% member fee, default false). Examples: {"gross":20000000}; {"gross":80000000,"nationality":"foreigner","as_of":"2026-08"}.

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": {
      "gross": "<gross>"
    },
    "name": "employer_cost"
  }
}

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.
grossYesMonthly gross salary in VND (whole number), e.g. 30000000.
monthNoSynonym of as_of (same formats: YYYY-MM or YYYY-MM-DD). Pass only one of as_of, month, date.
regionNoRegional minimum wage zone I, II, III or IV (default I); 1-4 and lower case are accepted. Chosen by the user; there is no locality lookup.
residencyNoTax residency: "resident" (default; progressive scale with deductions) or "non_resident" (flat 20% of gross, no deductions).
dependentsNoNumber of registered dependents (0-20, default 0). Residents only: 6.2 million VND per dependent per month.
nationalityNo"vietnamese" (default) or "foreigner" = foreign citizen with a labour contract of 12 months or more: social and health insurance, no unemployment insurance.
union_memberNoEmployee is a trade union member: deduct the 0.5% member fee (default false).
insurance_baseNoSalary used for compulsory insurance, if different from gross. Must not be below the regional minimum wage; capped at the ceilings automatically.

Output Schema

NameRequiredDescriptionDefault
netYes
pitYes
as_ofYes
grossYes
notesYes
regionYes
sourcesYes
employerYes
residencyYes
disclaimerYes
nationalityYes
data_versionYes
employee_contributionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world behavior, and the description goes well beyond them by disclosing the actual contribution rate structure, the foreigner exemption rule, automatic ceiling capping on insurance_base, the regional-minimum floor, and that there is no locality lookup. Two worked examples show expected call shapes, which is real behavioral context rather than annotation restatement.

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?

Purpose and rate breakdown are front-loaded and every clause carries information, with no filler. The structure is a single dense run-on sentence with heavy parenthetical nesting, which slightly hurts scannability of the options list.

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 10-parameter financial calculator with an output schema and full annotations, the description covers defaults, enum meanings, edge cases (non-resident flat 20%, foreigner contract threshold, insurance base floor/ceiling), and examples. Nothing an agent needs to invoke it correctly is missing.

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 a 3 is the baseline; the description earns above that by compactly restating the option set with interpretive detail ('foreigner = contract of 12 months or more', 'month and date are accepted as synonyms', 'region I-IV or 1-4 default I') and by supplying valid example payloads. It adds modest meaning over the schema rather than new parameter semantics.

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?

Names a specific verb and resource ('Calculate what a monthly gross salary costs an employer in Vietnam') and enumerates the exact components produced (SI 3%/14%/0.5%, health 3%, unemployment 1%, union 2%, total cost, employee net). This makes it clearly distinguishable from employee-side siblings like gross_to_net and net_to_gross without opening their schemas.

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?

Gives clear conditional guidance for each option: unemployment insurance is excluded 'not for foreigners', dependents are 'residents only', insurance_base applies only 'if the insured salary differs from gross'. It stops short of naming a sibling to use instead (e.g. when to prefer gross_to_net), so it is clear context without explicit alternatives.

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.