Skip to main content
Glama

Thuế hộ kinh doanh Việt Nam 2026

tinh_thue_hkd

Ước lượng thuế GTGT và TNCN một năm của hộ kinh doanh Việt Nam. Tiền tính bằng đồng. nganh: danh sách {nhom, doanh_thu}; nhom thuộc: hang_hoa, dich_vu, san_xuat_van_tai_an_uong, cho_thue_tai_san_khac, dai_ly_bh_xs_dacap, noi_dung_so, khac, cho_thue_bat_dong_san. chi_phi: chi phí cả năm (đồng), bắt buộc khi doanh thu trên 3 tỷ. Estimate annual VAT and personal income tax of a Vietnamese household business (amounts in VND). Kết quả kèm trường can_cu (văn bản pháp luật) và chua_xac_minh (khoản chưa xác minh, trả null thay vì đoán) và luu_y. Results include can_cu, chua_xac_minh and a disclaimer.

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": {
      "nganh": "<nganh>"
    },
    "name": "tinh_thue_hkd"
  }
}

Input Schema

NameRequiredDescriptionDefault
namNo
nganhYes
chi_phiNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful behavior: results are explicitly estimates, include a legal-basis field (can_cu), return null for unverified items instead of guessing (chua_xac_minh), and carry a disclaimer. It still says nothing about permissions, statelessness, or how the estimate degrades on unusual inputs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded and covers the right topics, but the entire substance is duplicated in Vietnamese and English, including the return-field notes, which nearly doubles the length without adding information. A single language or a tighter bilingual mix would read better.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the description deliberately highlights the non-obvious return fields (can_cu, chua_xac_minh, luu_y), which is the right level of detail. The main gap is the undocumented nam parameter and the absence of any note on how the year affects the tax rules applied.

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 0%, so the description must compensate, and it largely does: it spells out the nganh list shape {nhom, doanh_thu}, enumerates all eight valid nhom values, and explains chi_phi's meaning and its revenue-conditional requirement. The nam (year) parameter is never mentioned, leaving one of three inputs undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: estimate annual VAT (GTGT) and personal income tax (TNCN) for a Vietnamese household business, with amounts in VND. The domain is narrow enough to be distinguishable from the sibling calculators, but no sibling is named or contrasted, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The only conditional rule given is domain logic: chi_phi is required when annual revenue exceeds 3 billion VND. There is no statement of when to pick this tool over tra_nguong_doanh_thu or when it is inappropriate (e.g., non-household-business entities), so usage is implied rather than guided.

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.

Resources