Skip to main content
Glama

Vietnam Payroll and Tax Calculator

Parameters, acts and coverage

data_info
Read-onlyIdempotent

Return the parameters this calculator uses for each period from January 2026 (tax scale, family deductions, base salary, insurance ceilings, regional minimum wages, contribution rates, trade union rates, lump-sum rules, adjustment coefficients) with act numbers and verification status, the rounding rule, what is not included, and the data version. Use when the user asks how current or reliable the figures are. Takes no arguments: {}.

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": "data_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
data_dateYes
disclaimerYes
parametersYes
data_versionYes
supported_fromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint=false, destructiveHint=false). The description adds real substance beyond them: verification status, act numbers, the rounding rule, explicit disclosure of "what is not included", and a data version. Not quite 5 only because it does not mention limits such as period coverage boundaries beyond "from January 2026".

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 verb and scope, and the trailing usage sentence and no-arg statement are each useful. The long parenthetical inventory of figure types is dense but every item earns its place by telling the agent what data is available.

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-argument read-only introspection tool with an output schema already present, nothing material is missing. The description states what data is returned, its provenance and verification status, and that no inputs are needed.

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

Parameters3/5

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

The tool takes zero parameters, and the description confirms this with "Takes no arguments: {}", which matches the empty schema. With no parameters to explain, there is no additional semantic value the description could add here, so the baseline score applies.

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?

Opens with a specific verb and resource ("Return the parameters this calculator uses for each period") and enumerates the exact contents, including act numbers, verification status, rounding rule and data version. That detail distinguishes it from the sibling calculators (gross_to_net, pit_only, etc.), which compute figures rather than describe them.

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 an explicit trigger: "Use when the user asks how current or reliable the figures are." That is clear context for selection. It stops short of naming an alternative or stating when not to use it, so it lands at 4 rather than 5.

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.