Skip to main content
Glama

Skyalo Travel Connectivity Guide

Check an exact phone's eSIM readiness

check_esim_device_compatibility
Read-onlyIdempotent

Use this tool whenever the user asks whether a phone supports eSIM or is ready for a travel eSIM. Check an exact phone model against Skyalo's manufacturer-sourced compatibility catalog, including regional variants, carrier locks, EID, and Add eSIM settings. Do not call build_travel_connectivity_guide for a pure device question. Unknown never means incompatible. This tool does not search, compare, recommend, price, sell, or link to connectivity plans.

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": {
      "model": "<model>"
    },
    "name": "check_esim_device_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesExact phone model, for example Samsung Galaxy S24 or Apple iPhone 15; not a broad product family.
localeNo
regionNoCountry or sales region of the exact device variant.
eidPresentNo
manufacturerNo
carrierUnlockedNo
addEsimSettingPresentNo

Output Schema

NameRequiredDescriptionDefault
checksNo
deviceNo
localeNo
reasonNo
sourceYes
statusYes
guidanceNo
suggestionsNo
catalogStatusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / locale
      Added value: +{
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / model / description
      Previous value: -"Exact phone model, not a broad product family."New value: +"Exact phone model, for example Samsung Galaxy S24 or Apple iPhone 15; not a broad product family."
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, and the description adds genuinely new context: the catalog is manufacturer-sourced, results account for regional variants, carrier locks, EID, and Add eSIM settings, and 'Unknown never means incompatible' defines how to interpret an inconclusive result. That interpretive rule is the kind of detail structured fields cannot carry.

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?

The trigger condition is front-loaded in the first sentence, followed by the mechanism, the sibling exclusion, and the scope boundary, with no filler. The one weak spot is that the 'does not search, compare, recommend, price, sell, or link' clause is a long enumeration that partly repeats the earlier sibling warning.

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 7-parameter read tool with an output schema and strong annotations, the description covers purpose, invocation trigger, sibling routing, and result interpretation. The remaining gap is that most optional parameters are undocumented in both the schema and the description, which matters for a compatibility lookup where the agent may supply partial device facts.

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 coverage is only 29%, so the description must compensate, and it partially does: 'regional variants, carrier locks, EID, and Add eSIM settings' maps onto region, carrierUnlocked, eidPresent, and addEsimSettingPresent. However, locale and manufacturer are never mentioned, and the description does not say how the booleans are used (as filters versus corroborating signals), so an agent still has to infer the calling semantics.

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 and resource ('Check an exact phone model against Skyalo's manufacturer-sourced compatibility catalog') and enumerates the dimensions checked: regional variants, carrier locks, EID, and Add eSIM settings. It also draws a hard boundary against plan-search and recommendation siblings, so an agent can separate it from build_travel_connectivity_guide and search_skyalo_esim_plans without opening any schema.

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

Usage Guidelines5/5

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

It gives an explicit trigger ('whenever the user asks whether a phone supports eSIM or is ready for a travel eSIM'), an explicit exclusion ('Do not call build_travel_connectivity_guide for a pure device question'), and a negative scope list (no search, compare, recommend, price, sell, or link). When-to-use, when-not-to-use, and the alternative are all present.

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