esimoa — travel eSIM comparison

Search & compare travel eSIMs

search_esims

Read-onlyIdempotent

Search the travel eSIM catalog of esimoa (이심모아) and compare plans for a destination. Filter by trip length, data, unlimited or daily data, local phone number, local or roaming network, multi-country coverage, price, provider, hotspot and 5G. Sort by "recommended" (esimoa’s default order), "price" (lowest first), "data" (most data first), "price_per_gb" or "validity" (longest first). Each result includes its id (for get_esim and compare_esims) and a url to the plan page on esimoa.com. Prices are in KRW.

Input Schema

TableJSON Schema

Name	Required	Description
`days`	No	Trip length in days. Plans covering at least this many days (and not much longer) are returned.
`lang`	No	Language for country names and the plan page. Match the user’s language (ko, en, ja, zh-CN, zh-TW, es, fr, ar, vi, th, id, it, de).
`sort`	No	recommended \| price \| data \| price_per_gb \| validity
`limit`	No	Number of plans (default 5, max 10).
`five_g`	No	true = 5G network. Checked within the top 50 matches, so the total is approximate.
`country`	No	Destination country — ISO code (JP) or name in any language (Japan, 일본).
`data_gb`	No	Minimum data needed in GB.
`hotspot`	No	true = hotspot/tethering supported. Checked within the top 50 matches, so the total is approximate.
`network`	No	local = local carrier network (usually faster); roaming = roaming network.
`provider`	No	Provider code exactly as returned in results (e.g. from a previous search).
`countries`	No	Multi-country trip — only plans that work in ALL of these countries (ISO codes or names). Use instead of country.
`data_type`	No	daily = data allowance resets every day; total = one allowance for the whole trip.
`unlimited`	No	Only unlimited-data plans.
`max_data_gb`	No	Maximum data in GB.
`local_number`	No	true = only plans that include a local phone number for calls/SMS.
`max_price_krw`	No	Maximum price in KRW (budget).
`min_price_krw`	No	Minimum price in KRW.
`multi_country`	No	true = multi-country (regional) plans only; false = single-country plans only.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No
`sort`	No
`items`	Yes
`total`	Yes
`totalIsApproximate`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 2, 2026

changedInput schema / properties / lang / description

Previous value: -"Language for country names and the purchase page. Match the user’s language (ko, en, ja, zh-CN, zh-TW)."New value: +"Language for country names and the plan page. Match the user’s language (ko, en, ja, zh-CN, zh-TW, es, fr, ar, vi, th, id, it, de)."

changedInput schema / properties / lang / enum

Previous value: -[
-  "ko",
-  "en",
-  "ja",
-  "zh-CN",
-  "zh-TW"
-]New value: +[
+  "ko",
+  "en",
+  "ja",
+  "zh-CN",
+  "zh-TW",
+  "es",
+  "fr",
+  "ar",
+  "vi",
+  "th",
+  "id",
+  "it",
+  "de"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "items": {
+        "properties": {
+          "countryCode": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "countryName": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "coverageCountries": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "currency": {
+            "enum": [
+              "KRW"
+            ],
+            "type": "string"
+          },
+          "dataAmount": {
+            "type": "string"
+          },
+          "dataAmountGB": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "dataType": {
+            "description": "daily | total | null (unknown)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "hasLocalNumber": {
+            "type": "boolean"
+          },
+          "hotspot": {
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "isLocalNetwork": {
+            "type": "boolean"
+          },
+          "isMultiCountry": {
+            "type": "boolean"
+          },
+          "isUnlimited": {
+            "type": "boolean"
+          },
+          "networkType": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "priceKrw": {
+            "type": "number"
+          },
+          "provider": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "description": "Plan page on esimoa.com",
+            "type": "string"
+          },
+          "validityDays": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "priceKrw",
+          "currency",
+          "validityDays",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "lang": {
+      "enum": [
+        "ko",
+        "en",
+        "ja",
+        "zh-CN",
+        "zh-TW",
+        "es",
+        "fr",
+        "ar",
+        "vi",
+        "th",
+        "id",
+        "it",
+        "de"
+      ],
+      "type": "string"
+    },
+    "sort": {
+      "enum": [
+        "recommended",
+        "price",
+        "data",
+        "price_per_gb",
+        "validity"
+      ],
+      "type": "string"
+    },
+    "total": {
+      "type": "number"
+    },
+    "totalIsApproximate": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "items",
+    "total"
+  ],
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description's added context is meaningful: results carry an `id` usable by get_esim/compare_esims, a `url`, and prices are denominated in KRW, plus the note that 'recommended' is esimoa's default order. It omits pagination/rate-limit behavior, keeping it just below the top.

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?

Purpose and filter set are front-loaded, then sorts, then result shape and currency — a logical order with essentially no filler. It is a dense list rather than a tightly structured paragraph, but every clause contributes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 18 parameters at 100% schema coverage, an output schema for return values, and read-only annotations, the description carries only the remaining burden and does so: purpose, filter/sort vocabulary, result fields, and downstream tool wiring. It is close to complete for a tool of this complexity, with only pagination-like behavior unaddressed.

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 description coverage is 100%, so the baseline is 3. The description genuinely adds meaning the schema lacks: the sort enum's semantics ('price' = lowest first, 'data' = most data, 'validity' = longest first) and the fact that 'recommended' is the default, information the schema's bare enum listing does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Search the travel eSIM catalog of esimoa and compare plans for a destination') and names sibling tools by explaining that each result's `id` feeds get_esim and compare_esims. That establishes its role in the tool family, though it never explicitly contrasts itself with compare_esims, so differentiation is indirect rather than stated.

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 provides clear usage context: search by destination/trip length with an enumerated filter set, sort with named orders, and hand result ids to get_esim/compare_esims. There is no explicit 'use this instead of X when…' exclusion, so it stops short of the top band.

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

All esimoa — travel eSIM comparison tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.