Skip to main content
Glama

Vietnam Payroll and Tax Calculator

Net to gross salary (Vietnam)

net_to_gross
Read-onlyIdempotent

Find the gross monthly salary that gives a desired net (take-home) pay in Vietnam, for offers quoted in net. Exact to the dong: target_net and net_difference show the match. Returns the same breakdown as gross_to_net (insurance by fund, deductions, tax by bracket, employer cost). 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: {"net":25000000}; {"net":40000000,"dependents":1,"as_of":"2027-02"}.

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": {
      "net": "<net>"
    },
    "name": "net_to_gross"
  }
}

Input Schema

NameRequiredDescriptionDefault
netYesDesired monthly net (take-home) salary in VND, e.g. 25000000.
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.
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.4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description goes beyond them by promising exactness to the dong with target_net and net_difference as the match signal, and by explaining the side effects of options (foreigner contracts lose unemployment insurance, insurance_base cannot fall below the regional minimum).

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?

The core definition and the exact-match guarantee are front-loaded, and the two examples are compact and useful. The middle "Options:" clause restates nearly every schema field with its default, which is convenient but largely redundant against 100% schema coverage.

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 inverse calculator with an output schema and full annotation coverage, nothing an agent needs is missing: direction of the computation, exactness semantics, defaults, enum meanings, a validation constraint, and concrete call examples. Return values are documented separately, so the description rightly does not re-specify them.

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 description coverage is 100%, so the baseline is 3; the description earns an extra point by adding interpretive meaning beyond the field docs, notably that foreigner implies a contract of 12 months or more and therefore no unemployment insurance, and that region is user-chosen with no locality lookup. Much of the option list duplicates the schema, which caps it below 5.

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?

"Find the gross monthly salary that gives a desired net (take-home) pay in Vietnam" names a specific inverse computation and resource, and adds the qualifying context "for offers quoted in net." It also tells the agent it returns the same breakdown as gross_to_net, which separates it from that sibling without needing 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 phrase "for offers quoted in net" gives a clear selection condition, implicitly routing gross-quoted queries to gross_to_net. It stops short of an explicit "use gross_to_net when you have a gross figure" exclusion, so the inverse relationship must be inferred from the shared-breakdown sentence.

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.