Skip to main content
Glama

Thuế hộ kinh doanh Việt Nam 2026

tinh_tra_gop

Lập lịch trả góp từng kỳ (gốc, lãi, tổng, còn lại). so_tien: số vay (đồng); lai_suat_nam_pct: lãi suất %/năm do người dùng cung cấp; so_thang: số tháng (tối đa 1200); kieu: du_no_giam_dan (gốc chia đều, lãi trên dư nợ) hoặc tra_deu (niên kim, mỗi kỳ trả cố định). Build a loan repayment schedule (amount in VND, rate in %/year, term in months). 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": {
      "so_tien": "<so_tien>",
      "lai_suat_nam_pct": "<lai_suat_nam_pct>",
      "so_thang": "<so_thang>"
    },
    "name": "tinh_tra_gop"
  }
}

Input Schema

NameRequiredDescriptionDefault
kieuNodu_no_giam_dan
so_tienYes
so_thangYes
lai_suat_nam_pctYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it discloses meaningful behavior: the term is capped at 1200 months, the returns carry a 'can_cu' field with the controlling legal text, unverified items are returned as null rather than guessed ('chua_xac_minh'), and a disclaimer ('luu_y') accompanies output. What it omits is rounding conventions and whether the schedule is returned as a full table or summarized, which matters for a 1200-month worst case.

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 parameter semantics are front-loaded and useful, but the text is redundant: the Vietnamese and English renderings of the purpose restate each other, and the final sentence repeats can_cu and chua_xac_minh already introduced earlier. The mixed-language duplication costs space without adding information.

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?

For a four-parameter pure-computation tool with an output schema, this is close to complete: every parameter is explained, the two calculation modes are defined, and the tool-specific output fields (can_cu, chua_xac_minh, luu_y) are flagged even though the output schema covers their structure. The missing piece is precision on rounding and on output volume for long terms.

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 0% and the schema gives only bare titles, so the description must compensate, and it does: so_tien is the loan amount in VND, lai_suat_nam_pct is an annual percentage rate supplied by the user, so_thang is the term in months with a 1200 cap, and kieu is explained with both of its allowed string values and their financial meaning. This adds real semantic content the schema does not contain, including the enum values that the schema only hints at via a default.

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 names a specific verb and resource: 'Lập lịch trả góp từng kỳ (gốc, lãi, tổng, còn lại)', i.e. build a per-period loan amortization schedule with principal, interest, total and remaining balance. The financial domain is unmistakable, which separates it from siblings such as tinh_lai_tiet_kiem or tinh_thue_hkd, though it never names an alternative explicitly.

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?

Usage is only implied: the parameter explanation for 'kieu' contrasts du_no_giam_dan (equal principal, interest on outstanding balance) against tra_deu (annuity, fixed payment per period), which does guide the agent's choice of method. There is no statement of when to use this tool versus the savings-interest or tax siblings, and no prerequisites or exclusions.

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