Skip to main content
Glama

Vietnam Address Converter (2025 reform)

Dataset version and sources

data_info
Read-onlyIdempotent

Return the dataset version, the official source (National Statistics Office of Viet Nam transition table, with checksum and fetch date), the list of resolutions with issue and effective dates (2025 reform and 2026 changes), unit counts and the coverage note. Use when the user asks how current or reliable the data is. Takes no arguments: {}.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the provenance artifacts returned (checksum, fetch date, source identity, resolution issue/effective dates) and by confirming it takes no arguments. It stops short of describing output format or shape, but a metadata tool has little behavioral risk left to disclose.

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 description is front-loaded with the return contents, followed by usage guidance and an argument note; every clause carries information. The first sentence is long and list-dense, which slightly hurts scannability, but there is no filler.

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 carries the burden of describing return values, and it does so thoroughly (version, source, checksum, fetch date, resolutions, unit counts, coverage note). Combined with the explicit no-argument statement and the annotation-covered safety profile, an agent has everything needed to call and interpret this tool.

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 zero parameters, the baseline is 4, and the description reinforces this by explicitly stating "Takes no arguments: {}," matching the empty input schema. There is nothing further the description could add on parameter semantics.

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 opens with a specific verb ("Return") and enumerates exactly what is returned: dataset version, official source with checksum and fetch date, resolutions with issue/effective dates, unit counts, and the coverage note. This is clearly a provenance/metadata tool, easily distinguished from the sibling operations (convert_old_to_new, find_units, list_provinces, etc.).

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?

It gives an explicit trigger: "Use when the user asks how current or reliable the data is," which maps the tool to a recognizable user intent. It does not name an alternative or state when not to use it, but the provenance role is unambiguous relative to the listed siblings.

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.