Skip to main content
Glama

Vietnam Payroll and Tax Calculator

Regional minimum wage (Vietnam)

minimum_wage
Read-onlyIdempotent

Return Vietnam's regional minimum wages (monthly and hourly, regions I-IV) in force on a date from January 2026, including the new rates from 1 January 2027, with the unemployment insurance ceiling of each region (20 x the minimum). The region of a workplace is set by the decree's annex of communes; this tool does not look it up. Examples: {}; {"as_of":"2027-02","region":"I"}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "minimum_wage"
  }
}

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.
regionNoOptional region I-IV (or 1-4) to single out; all four regions are always listed.

Output Schema

NameRequiredDescriptionDefault
as_ofYes
notesYes
regionsYes
sourcesYes
disclaimerYes
data_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real context beyond that: the effective-date behavior (a date from January 2026 onward, with distinct 2027 rates) and the important caveat that region assignment is a legal/geographic lookup this tool will not perform. It does not discuss how the 2027 rates differ or any rate-limit/precision caveats, keeping it below top marks.

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 description is front-loaded with the return payload, then the date-range rule, then the region caveat, then examples — a sensible order with no filler sentences. It is dense (the decree/annex clause is a single long sentence) and the examples are run together inline, which slightly hurts scannability, but every element carries information.

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 zero-required-parameter, read-only reference lookup with an output schema, this covers everything an agent needs: what is returned, the valid date window, default behavior, region semantics, and the explicit statement that region lookup is out of scope. Return-value structure is correctly left to the output schema.

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

Parameters5/5

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

Schema description coverage is 100%, so the schema already documents as_of/month/date synonyms and the region enum, making the baseline 3. The description earns above baseline by showing concrete call shapes (empty object for defaults, and an explicit as_of plus region I example), which clarifies how the optional region filter behaves alongside the default date. The examples directly resolve the main ambiguity an agent would face: whether to pass anything at all.

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?

The description opens with a specific verb and resource — "Return Vietnam's regional minimum wages (monthly and hourly, regions I-IV)" — and pins down the exact time scope (in force on a date from January 2026, plus new rates from 1 January 2027) and the derived value returned (unemployment insurance ceiling = 20x minimum). It is unambiguous and clearly distinct from the payroll/net-to-gross siblings in the catalog.

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?

It states the supported date range implicitly via "in force on a date from January 2026" and, critically, sets a scope boundary: the tool does not resolve a workplace's region because that is fixed by the decree's annex of communes. Call examples ({}, {"as_of":"2027-02","region":"I"}) show the intended invocation patterns. It stops short of naming a sibling tool for payroll calculations, so no explicit alternative is offered.

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.