Skip to main content
Glama
Sign In
vietnam-address-mcp

vietnam-address-mcp

by amItuff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Normalize many Vietnamese addresses at once

normalize_addresses
Read-onlyIdempotent

Batch-normalize up to 200 Vietnamese addresses, converting old three-level formats into the current 34-province, district-free structure and flagging ambiguous or not-found entries for review.

Instructions

Batch version of normalize_address for up to 200 addresses (for example a column of a customer or order spreadsheet). Returns one result per input in the same order plus a summary of how many are ok, ambiguous, not_found or divided-ward defaults. Review ambiguous and not_found items with the user instead of guessing. Chuẩn hóa hàng loạt địa chỉ cũ sang địa chỉ mới.

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": {
      "addresses": "<addresses>"
    },
    "name": "normalize_addresses"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressesYesComma-separated addresses, each in old or new format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the description only needs to add beyond that. It does: results come back one per input in the same order, and a summary tally of ok / ambiguous / not_found / divided-ward defaults is returned, which is meaningful disclosure for a no-output-schema 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 batch scope, the size limit, and the return shape in three dense sentences with no filler. The closing Vietnamese sentence largely restates what the English text already said, which is slight redundancy for the marginal benefit of matching user phrasing.

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?

For a one-parameter read-only batch tool with no output schema, the description covers scope, input example, ordering guarantee, per-item status vocabulary, and how to handle unresolved items. Nothing an agent needs to call and interpret the result correctly is missing.

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?

There is a single parameter at 100% schema coverage, where the schema already documents min/max length and the 200-item cap. The description reinforces the 200 limit and gives a realistic input source (a spreadsheet column) but adds no format or syntax detail beyond the schema.

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?

Opens with a specific verb and resource ("Batch version of normalize_address") plus an explicit scope bound of 200 addresses, and names the sibling it extends so the agent can distinguish batch from single-address normalization immediately.

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?

The batch framing and the example ("a column of a customer or order spreadsheet") make clear this is for many addresses rather than one, and "Review ambiguous and not_found items with the user instead of guessing" gives post-call handling guidance. There is no explicit "use normalize_address for a single address" statement, so routing to the sibling is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools