Skip to main content
Glama

Vietnam Address Converter (2025 reform)

Rewrite a free-form address to the new units

normalize_address
Read-onlyIdempotent

Parse a free-form Vietnamese address line (street, commune, district, province; with or without diacritics, commas or abbreviations) and rewrite it with the post-reform units: drops the district and replaces the old commune and province. Returns status (converted, already_new, province_level when only a province was given, ambiguous, partial when the commune is missing, e.g. a district alone, not_found), confidence, the rewritten address, all candidates when ambiguous, which parts were recognised and which were not. Never invents a unit. Examples: {"address":"12 Nguyễn Huệ, P. Bến Nghé, Q.1, TP.HCM"}; {"address":"so 1 phu cuong thu dau mot binh duong"}.

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": {
      "address": "<address>"
    },
    "name": "normalize_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesFree-form Vietnamese address, with or without diacritics, e.g. "12 Nguyễn Huệ, P. Bến Nghé, Q.1, TP.HCM" or "so 1 phu cuong thu dau mot binh duong".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover read-only, idempotent, non-destructive, and closed-world, so the description carries the burden and does so: it enumerates every status outcome (converted, already_new, province_level, ambiguous, partial, not_found), names the other returned fields (confidence, rewritten address, candidates, recognised/unrecognised parts), and adds the strong guarantee 'Never invents a unit'. That is exactly the behavioral context an agent needs to trust and interpret results.

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 transformation is front-loaded in the first clause and the return-value enumeration follows logically; nothing is padding. The middle status parenthetical is a long run-on that slightly hurts scanning, and the two examples overlap with the schema description, but the density is mostly earned.

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?

There is no output schema, so the description must explain the return shape, and it does so exhaustively: status values, confidence, rewritten address, candidate list, and recognition flags. Combined with the no-invention guarantee and worked examples, an agent has everything needed to call this correctly and interpret edge cases.

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?

With one parameter and 100% schema coverage, the baseline is 3, but the description adds genuine meaning beyond the schema by spelling out that the line may contain street, commune, district and province components and that commas, abbreviations and missing diacritics are all acceptable. This helps the agent decide what input to construct rather than merely passing a string.

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 states a specific verb and resource (parse and rewrite a free-form Vietnamese address) and specifies the transformation precisely: drops the district and replaces the old commune and province with post-reform units. The parenthetical breakdown of address components and tolerated input variations makes the scope unambiguous.

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 implied by the purpose (use when you have a free-form address string to modernise), and the status vocabulary ('province_level when only a province was given', 'partial when the commune is missing') hints at input expectations. However, it never says when to prefer this over the near-identical sibling convert_old_to_new, nor states prerequisites or when-not-to-use; the agent must infer the routing.

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.