Skip to main content
Glama
Sign In

esimoa — travel eSIM comparison

by com.esimoa
OverviewDiscussionsAdmin

List eSIM destinations

list_countries
Read-onlyIdempotent

List countries where esimoa (이심모아) sells eSIMs, with the number of plans and the lowest price (KRW). Optionally filter by name.

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

Input Schema

NameRequiredDescriptionDefault
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).
queryNoCountry name or ISO code filter

Output Schema

NameRequiredDescriptionDefault
itemsYes
totalYes

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": {
+    "items": {
+      "items": {
+        "properties": {
+          "countryCode": {
+            "type": "string"
+          },
+          "lowestPriceKrw": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "planCount": {
+            "type": "number"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "countryCode",
+          "name",
+          "planCount",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "items",
+    "total"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds genuinely useful context by disclosing that the catalog is limited to esimoa's destinations and that price is returned in KRW with a plan count. It stops short of mentioning pagination or result-size behavior.

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 that leads with the resource being listed, then the returned fields, then the filter. No filler.

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?

For a two-parameter read-only list tool with an output schema and full annotation coverage, the description is nearly complete; the main omission is guidance on how this list relates to the sibling search/compare tools.

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%, so both parameters (lang enum, query filter) are already documented in the schema. The description only echoes the name filter and never mentions the language parameter, adding no syntax or format 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?

States a specific verb+resource ('List countries where esimoa sells eSIMs') plus the returned fields (plan count, lowest price in KRW) and the optional filter. An agent can distinguish this catalog-listing tool from compare_esims/search_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 Guidelines3/5

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

Says 'Optionally filter by name,' which implies a lookup use case, but gives no explicit when-to-use guidance or criteria for choosing this over search_esims or search. Usage is only weakly implied.

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