Skip to main content
Glama

VN GroundTruth

check_entry

Read-only

Is a traveler of a given nationality visa-exempt for Vietnam on a given arrival date and purpose? Returns status, max stay, legal basis, validity window (including the 2028 expiry of unilateral exemptions), tourism-only flag, source and official e-visa domains.

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": {
      "nationality": "<nationality>"
    },
    "name": "check_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
purposeNodefaults to tourism
nationalityYesISO 3166-1 alpha-2 code (e.g. DE) or English country name
arrival_dateNoYYYY-MM-DD, defaults to today

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), and the description adds substantial context beyond them: it enumerates the returned fields (status, max stay, legal basis, validity window), flags a real data caveat (the 2028 expiry of unilateral exemptions), notes a tourism-only flag, and discloses provenance/source plus e-visa domains. It stops short of saying how authoritative or fresh the underlying rules are, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: the question is front-loaded and the return-value list follows immediately, with no filler. Every clause (2028 expiry, tourism-only flag, source domains) conveys distinct information an agent would otherwise have to discover at runtime.

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 must describe what comes back — and it does, listing status, max stay, legal basis, validity window, tourism-only flag, and sources. Combined with the safety annotations and fully documented schema, 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with formats, enum, and defaults all documented in the schema itself, so the schema carries the parameter burden. The description only restates that nationality, arrival date, and purpose are inputs, adding no format or edge-case guidance beyond it — the baseline 3 applies.

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 frames a precise, specific question — visa exemption for a given nationality, arrival date, and purpose, scoped to Vietnam — which is a clear verb+resource statement an agent can match to a user intent without opening the schema. It is obviously distinct from the sibling tools (quota_status, motorbike_rules, ha_long_disruptions, official_evisa_domains).

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

Usage Guidelines3/5

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

Usage is implied by the question phrasing: it is clearly the tool for 'is X nationality exempt?' queries, and the mention of 'official e-visa domains' hints at a related decision path. However, it never states when to prefer this over official_evisa_domains or quota_status, and gives no prerequisites or exclusions.

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.

Resources