Skip to main content
Glama

Skyalo Travel Connectivity Guide

Search current Skyalo eSIM plans

search_skyalo_esim_plans
Read-onlyIdempotent

Search current first-party Skyalo travel eSIM inventory for a country or region. Use only when the user explicitly asks for a Skyalo plan or current eSIM plan options. Returns factual data allowance, validity, availability, and USD price from Skyalo's backend. This is not a comparison of all providers and must not be described as best or cheapest across the market. Search results never include a purchase action. If the user later selects an exact displayed planId and explicitly asks to buy it, use prepare_skyalo_purchase_handoff.

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": {
      "destination": "<destination>"
    },
    "name": "search_skyalo_esim_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoBCP 47 language override; otherwise use the ChatGPT locale.
hotspotNo
currencyNoISO 4217 currency. This release exposes authoritative USD prices only.USD
planTypeNoany
travelersNo
destinationYesCountry name, ISO country code, localized destination name, common alias, or supported Skyalo region.
destinationTypeNoUse auto unless the user explicitly distinguishes a country from a region.auto
requestedDataGbNoRequested or estimated total data in GB.
requestedDurationDaysNoTrip length or minimum desired plan validity in days.

Output Schema

NameRequiredDescriptionDefault
plansNo
queryNo
localeNo
reasonNo
sourceYes
statusYes
filtersNo
freshnessNo
destinationNo
lastUpdatedNo
limitationsNo
suggestionsNo
externalCheckoutNo
requestedCurrencyNo
supportedCurrenciesNo
purchaseHandoffAvailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / locale / default
      Removed value: -"en"
    • changedInput schema / properties / locale / description
      Previous value: -"BCP 47 language tag for display formatting."New value: +"BCP 47 language override; otherwise use the ChatGPT locale."
    • addedOutput schema / properties / locale
      Added value: +{
      +  "type": "string"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is largely covered. The description still adds real value by disclosing the data source ('Skyalo's backend'), the returned facts (allowance, validity, availability, USD price), and the guarantee that results never include a purchase action. It stops short of error behavior, empty-result handling, or the USD-only currency constraint that the schema hints at.

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?

Four sentences, front-loaded with purpose then usage then returned data then the sibling handoff. Every sentence does work, including the anti-overclaiming guardrail. Minor redundancy between 'not a comparison of all providers' and 'must not be described as best or cheapest', which are two facets of the same constraint.

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 elaboration, and annotations cover the safety profile. The description is complete enough on scope, sourcing, and next-step routing for a 9-parameter read tool. The remaining gap is input-side semantics for the eight optional filtering parameters, which neither description nor schema fully documents.

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 67% across 9 parameters, so the schema carries most of the burden and the baseline is 3. The description names no input parameter at all and does not explain destination vs destinationType, hotspot, travelers, or how requestedDataGb/requestedDurationDays filter results; 'planId' is a returned field, not an input. It therefore adds no meaning 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 and resource with explicit scope: 'Search current first-party Skyalo travel eSIM inventory for a country or region.' The word 'first-party' and 'Skyalo' narrow it away from a general eSIM comparison, and the closing sentence names the sibling prepare_skyalo_purchase_handoff so the agent can separate search from purchase.

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?

Gives an explicit when: 'Use only when the user explicitly asks for a Skyalo plan or current eSIM plan options.' Gives an explicit when-not: it is not an all-provider comparison and must not be framed as best/cheapest. It also routes the purchase case to a named alternative with a concrete condition (exact displayed planId plus explicit buy intent).

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