Skip to main content
Glama

Skyalo Travel Connectivity Guide

Open a selected Skyalo plan for purchase

prepare_skyalo_purchase_handoff
Read-onlyIdempotent

Prepare an external Skyalo product-page handoff only after the user explicitly selects an exact planId returned by search_skyalo_esim_plans and asks to buy it. Re-read current Skyalo inventory, match that exact planId, and return one allowlisted product-page URL. The purchase, authentication, order creation, payment, delivery, activation, installation, wallet, balance, and top-up occur outside ChatGPT. Never call this tool from a browsing or comparison request alone.

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>",
      "planId": "<planId>"
    },
    "name": "prepare_skyalo_purchase_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNo
planIdYesExact planId returned by search_skyalo_esim_plans and explicitly selected by the user.
planTypeNoThe same plan-type filter used for the preceding plan search.any
destinationYesThe same country or region used for the plan search.
requestedDataGbNoThe same data filter used for the preceding plan search, when present.
requestedDurationDaysNoThe same duration filter used for the preceding plan search, when present.

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. Changed2 schema fields changed
    • removedInput schema / properties / locale / default
      Removed value: -"en"
    • addedOutput schema / properties / locale
      Added value: +{
      +  "type": "string"
      +}
  2. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context — that purchase, auth, order creation, payment, delivery, activation, installation, wallet, balance and top-up happen outside ChatGPT, and that inventory is re-read and matched at call time. It stops short of describing failure modes (e.g. planId no longer available) or rate limits, so beyond-annotation value is real but not exhaustive.

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?

Three sentences, front-loaded with the precondition before the behavior. The enumerated list of steps occurring outside ChatGPT is long but each item is load-bearing for scoping the tool. Some compression (e.g. "payment, delivery and activation") would tighten it further.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-required-parameter handoff tool with full annotations and an output schema, the description covers the trigger condition, the read-only validation behavior, and the exact scope boundary. Nothing an agent needs in order to call it correctly is missing.

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 83%, so the schema already documents each filter parameter and its tie to the preceding search. The description reinforces that the planId must be the exact one returned by search, but adds no syntax, format, or default semantics beyond that. Baseline 3 is appropriate.

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 — prepare an external Skyalo product-page handoff returning one allowlisted product-page URL — and explicitly distinguishes the step that follows from the search step. An agent can tell it apart from search_skyalo_esim_plans without opening either 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?

Gives explicit preconditions (user must explicitly select an exact planId returned by search_skyalo_esim_plans and ask to buy) and an explicit exclusion ("Never call this tool from a browsing or comparison request alone"). Names the sibling it depends on, leaving nothing to inference.

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