Skip to main content
Glama

Vietnam Address Converter (2025 reform)

Explain how a new unit was formed

explain_merge
Read-onlyIdempotent

Explain what a NEW (post-1 July 2025) commune or province was formed from: the old communes or provinces merged into it, whether each came whole or partially (split communes list the other new units their parts went to), the transition type and the resolution numbers. Use when the user asks "which wards were merged into X" or needs the legal basis. Takes the new unit code (5 digits for a commune, 2 for a province); get it from find_units or convert_old_to_new. Examples: {"code":"26734"}; {"code":"79"}.

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": {
      "code": "<code>"
    },
    "name": "explain_merge"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesCode of a NEW unit: 5-digit commune code (e.g. "26734") or 2-digit province code (e.g. "79").

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds real value by enumerating the returned content (merged-from units, split destinations, transition type, resolution numbers). It stops short of saying what happens when the supplied code is not a NEW unit (e.g. a pre-2025 code), which is a meaningful edge case for this tool.

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 purpose and the trigger phrase before the mechanics and examples; every element (scope, source of code, format, examples) is useful. The long parenthetical clause makes it dense, but nothing is truly wasted.

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 a single required parameter, full schema coverage, and no output schema, the description carries the return-value explanation itself and does so thoroughly, plus it points to the tools needed to produce a valid input. An agent has everything required to invoke it correctly.

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 meaning beyond the schema: it explains where the code comes from (find_units / convert_old_to_new), the 5-digit vs 2-digit convention with intent, and concrete example values.

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 ("Explain") and a precise resource: what a post-1 July 2025 commune or province was formed from, including old units, whole-vs-partial merges, transition type and resolution numbers. It is clearly distinguishable from siblings like find_units and convert_old_to_new, which it names as the source of the code.

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 triggering conditions ("Use when the user asks 'which wards were merged into X' or needs the legal basis") and a prerequisite workflow: obtain the code from find_units or convert_old_to_new. Alternatives and when to use them are effectively named.

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.