Skip to main content
Glama

esimoa — travel eSIM comparison

by com.esimoa
OverviewDiscussionsAdmin

Get eSIM plan details

get_esim
Read-onlyIdempotent

Get the details of one esimoa (이심모아) eSIM plan by id (from search_esims), including its plan page url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPlan id
langNoLanguage 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).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemYes
langNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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": {
+    "item": {
+      "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"
+    },
+    "lang": {
+      "enum": [
+        "ko",
+        "en",
+        "ja",
+        "zh-CN",
+        "zh-TW",
+        "es",
+        "fr",
+        "ar",
+        "vi",
+        "th",
+        "id",
+        "it",
+        "de"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "item"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds only that the result includes the plan page url; it says nothing about rate limits, auth needs, or language-dependent output beyond what the schema states. With annotations carrying the main burden, a 3 is appropriate.

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?

A single front-loaded sentence with zero waste: verb and resource first, then the id provenance, then the notable return field. Nothing extraneous.

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?

An output schema exists, so return values need not be explained, and the rich annotations cover the safety semantics. The description is sufficient for a simple two-parameter lookup, with only minor room to mention the lang-driven output variation.

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 id and lang both documented in the schema (including the enum and the instruction to match the user's language), so the baseline is 3. The description adds provenance for id (from search_esims) but says nothing about the lang parameter's effect on output language.

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 states a specific verb (get) and resource (one esimoa eSIM plan's details) and pins scope with 'by id (from search_esims)'. It also names the sibling that produces the required id, letting an agent separate this from search_esims and compare_esims without opening a schema.

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 clearly conveys the retrieval context by telling the agent the id originates from search_esims, which is actionable routing guidance. However, it gives no exclusions or alternatives (e.g., use compare_esims when comparing plans), so guidance stops short of full when/when-not coverage.

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 toolsInspect
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.

Resources