Skip to main content
Glama
Sign In

esimgomobile — Travel eSIM Tools

by com.esimgomobile
OverviewDiscussionsAdmin

Coverage Checker

check_coverage
Read-onlyIdempotent

Use when the user asks whether a country is covered by esimgomobile plans. Answers from esimgomobile's published coverage list and plan catalog (pricing shown as catalog pricing only) plus the built-in country network reference.

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": {
      "country": "<country>"
    },
    "name": "check_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesCountry to check, e.g. Japan

Output Schema

NameRequiredDescriptionDefault
cardYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare safe read-only, idempotent, open-world behavior, so the description's remaining job is data-source disclosure, which it does: answers come from the published catalog and a built-in reference, with a clear caveat that pricing is catalog pricing only. It doesn't say the result reflects static published data rather than live availability, which would have closed the gap fully.

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, trigger first, source qualifications second, no filler. The parenthetical pricing caveat is dense but earns its place.

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 no explanation, and the source/caveat framing is present. What's missing is a note on what the tool cannot answer (e.g., live coverage changes), which matters for an open-world lookup.

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?

The single country parameter is fully documented in the schema (100% coverage, with an example). The description adds no format guidance (ISO code vs. name) beyond what the schema provides, so it sits at the baseline.

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?

States a specific question it answers — whether a country is covered by esimgomobile plans — and names the data sources behind the answer (coverage list, plan catalog, network reference). That separates it from generic listing tools like list_available_plans, though the check-vs-list distinction is implied rather than spelled out.

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?

"Use when the user asks whether a country is covered" is an explicit trigger condition, which is more than most siblings offer. It stops short of naming alternatives (e.g. list_country_networks or compare_plans) or stating when not to use it.

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

All esimgomobile — Travel eSIM Tools 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