Skip to main content
Glama

Vietnam Address Converter (2025 reform)

List provinces (34 new or 63 old)

list_provinces
Read-onlyIdempotent

List Vietnam's provinces and centrally-run cities. scope "new" (default): the 34 provinces in force since 1 July 2025, each with its code, number of communes and the old provinces merged into it. scope "old": the 63 provinces before the reform, each with the new province it became part of. Use for overviews or to answer "which provinces were merged into X". Example: {"scope":"old"}.

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

Input Schema

NameRequiredDescriptionDefault
scopeNo"new" (default): 34 provinces after 1 July 2025, with the old provinces merged into each. "old": 63 provinces before the reform, with the new province each went into.

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 the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add data-shape context — and it does, stating that each new-province entry carries its code, commune count and merged predecessors, and each old-province entry carries its successor. It does not mention ordering, response size, or whether pagination applies, which is the remaining gap.

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-loads the resource, then the scope semantics, then the use case and an example — a logical order with no filler. The only waste is the near-verbatim repetition of the scope definitions that already appear in the enum schema description.

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, but the description compensates by enumerating the fields returned per scope (code, commune count, merged-from / merged-into). For a single-enum, read-only listing tool this is everything an agent needs to call it and interpret the result.

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?

Schema description coverage is 100% and the only parameter is a documented enum, so the schema already carries the semantics. The description restates the same new/old distinction and adds a concrete example call, which is a small increment over the schema rather than new meaning.

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 ('List Vietnam's provinces and centrally-run cities') and immediately qualifies the two data sets the tool can return (34 new vs 63 old). This is enough for an agent to distinguish it from siblings like convert_old_to_new or explain_merge, which operate on single mappings rather than a full listing.

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 usage trigger ('Use for overviews or to answer "which provinces were merged into X"') and declares which scope is the default. It does not explicitly name the sibling tools that should be preferred for address conversion or merge explanation, so it stops short of full when-not guidance.

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.