Skip to main content
Glama

Vietnam Address Converter (2025 reform)

List communes of a province

list_wards
Read-onlyIdempotent

List all commune-level units (phường, xã, đặc khu) of one province. scope "new" (default): communes after the reform with codes and any 2026 changes; scope "old": communes as of 30 June 2025 with their district. The province may be a 2-digit code or a name. Example: {"province":"79"}; {"province":"Đà Nẵng","scope":"old"}. Output can be long (up to a few hundred entries); prefer find_units for a single name.

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": {
      "province": "<province>"
    },
    "name": "list_wards"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNo"new" (default): communes after the reform. "old": communes as of 30 June 2025, with their district.
provinceYesProvince: 2-digit code (e.g. "79") or name (e.g. "Hồ Chí Minh", "Ha Noi").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the description does not need to repeat the safety profile. It adds genuinely useful context beyond annotations: the result set can be large (up to a few hundred entries) and what each scope returns (codes plus 2026 changes vs. district assignment). It stops short of describing pagination or ordering, which keeps it below a 5.

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-loaded with the resource definition, then scope semantics, then input format, then the routing hint and size warning – a sensible priority order with almost no filler. Minor overlap between the description's scope text and the schema's own scope description, plus a slightly re-dundant restatement of province formats, keeps it from a 5.

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, yet the description still indicates what entries carry (codes, 2026 changes, district for old scope) and how large the response can get. Combined with the scope semantics and the sibling pointer, an agent has everything needed to call it correctly and anticipate the payload.

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 would be 3, but the description adds value by giving concrete call examples ('{"province":"79"}', '{"province":"Đà Nẵng","scope":"old"}') and restating that province accepts either a 2-digit code or a name. This makes the dual-input nature of province immediately actionable rather than something to be discovered in the pattern field.

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: listing commune-level units (phường, xã, đặc khu) within one province, and clarifies the vocabulary mismatch with the title's 'communes'. It also distinguishes itself from find_units for the single-name case, so an agent can route correctly without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit routing guidance ('prefer find_units for a single name') and explains the scope choice: 'new' for post-reform communes, 'old' for communes as of 30 June 2025 with their district. The default is stated, so no inference is required.

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.