Skip to main content
Glama

Vietnam Address Converter (2025 reform)

Convert old address to new (2025 reform)

convert_old_to_new
Read-onlyIdempotent

Convert a Vietnamese administrative address from BEFORE 1 July 2025 (old province, district, commune) to the unit(s) valid AFTER the 2025 reform. Use when the user has an old address, an old ID card or registration address, or asks "what is my ward called now". Pass the parts you have; names may be written with or without diacritics, with prefixes or abbreviations, or as official codes. Returns the old unit, the new commune and province, the new address line, transition type (merge, unchanged, rename, retype, special_zone), partial=true when only part of the old commune went there, and resolution numbers. If the old commune was split between several new communes, ALL of them are returned and ambiguous=true: do not pick one, ask for the street or hamlet. Examples: {"province":"TP.HCM","district":"Quận 8","ward":"Phường 16"}; {"province":"Bình Dương","district":"Thủ Dầu Một","ward":"Phú Cường"}; {"ward":"27430"}.

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

Input Schema

NameRequiredDescriptionDefault
wardNoOld commune-level unit (phường / xã / thị trấn): name, abbreviation (P.16) or 5-digit code.
districtNoOld district (quận / huyện / thị xã / thành phố): name, abbreviation (Q.1, H. Củ Chi) or 3-digit code.
provinceNoOld (pre-1 July 2025) province or city: name with or without diacritics, abbreviation (TP.HCM, HN) or 2-digit code. A post-reform province name is also accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world, so the description is free to spend its words on non-obvious behavior. It does: it discloses the returned fields (old unit, new commune and province, new address line, transition type with enumerated values, resolution numbers) and explains the two flags partial=true and ambiguous=true, including the operational consequence of the latter.

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

Conciseness5/5

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

Front-loaded with the transformation and its date boundary, then usage, then return shape, then the ambiguity rule, then worked examples. Every sentence carries a distinct fact: no restatement of the title, no filler, and the examples demonstrate three different input shapes rather than repeating one.

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?

With no output schema available, the description takes on the full burden of describing the response and does so completely, including the enumerated transition types and the two boolean flags. For a zero-required-parameter tool the 'pass the parts you have' instruction plus the split-commune fallback closes the main ways an agent could call it incorrectly.

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 coverage is 100%, so the baseline is 3; the description earns an extra point by generalizing input tolerance across all three fields (with or without diacritics, prefixes, abbreviations, or official codes) and by telling the agent it may pass only the parts it has, which is the practically important fact given that no parameter is required. It does not add format specifics beyond what the per-property schema text already says.

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?

States a specific verb and resource (convert a Vietnamese administrative address) plus an explicit direction and boundary: from BEFORE 1 July 2025 to units valid AFTER the 2025 reform. That temporal scoping cleanly separates it from any lookup or normalization sibling without needing to name 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 concrete triggering conditions: an old address, an old ID card or registration address, or the user asking 'what is my ward called now'. It also resolves the hardest decision case by instructing the agent not to pick among split results but to ask for street or hamlet. What is missing is an explicit exclusion or a named alternative for adjacent tasks (e.g., post-reform lookups).

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.