variotrip route eSIM configurator

Start secure checkout

start_checkout

Read-onlyIdempotent

Use only once the customer has decided to buy ("I'll take it", "how do I buy?"): the checkout handoff for one route (same input as quote_route). Returns the buy_url to give the customer, the final price and a ready-to-send checkout block (next_step, payment_methods, delivery) — on the page the route builder shows exactly this route; they press "Get it" and pay securely. No account needed; the eSIM is delivered on screen and by e-mail right after payment. No in-chat order tracking, no discount codes. For prices while the customer is still comparing, use quote_route.

Input Schema

TableJSON Schema

Name	Required	Description
`gb`	No	The data pool for the WHOLE route in whole GB (1–100), shared by every country. Omit = sized for normal use (1.5 GB × days). Not sure? Call recommend_config.
`days`	Yes	Trip length in days (1–90) for the whole route, counted from the first connection anywhere on the route.
`route`	Yes	The countries of the trip in travel order (1–8, each once).
`bucket`	No	Optional language-region bucket the customer shops in, e.g. en-gb, de-de (sets currency and link locale). Defaults from language.
`currency`	No	Optional ISO 4217 override for prices.
`language`	No	ISO language of the conversation, e.g. en, de, ja. Localizes country names and sets the language/currency of links and prices.

Output Schema

TableJSON Schema

Name	Required	Description
`days`	No	Trip length, counted from the first connection anywhere on the route.
`note`	No	Present when something about the request had to be adjusted — read it to the customer.
`price`	Yes	FULL price of this route in currency — the amount paid. Not per day, per GB or per country.
`route`	No	The countries on the eSIM in travel order with the networks of each.
`topup`	No	How the customer adds data, days or a country later (not through the tools).
`buy_url`	Yes	The route builder pre-set to exactly this route. Use verbatim.
`data_gb`	No	ONE data pool for every country on the route (whole GB), used wherever the customer is.
`hotspot`	No
`message`	No	A ready-to-send line for the customer.
`currency`	Yes
`delivery`	No	How and when the eSIM arrives.
`countries`	No
`next_step`	Yes	What the customer does now: open buy_url, press "Get it", pay.
`price_basis`	No
`not_available`	No	Requested countries variotrip cannot add (left out of the quote).
`price_is_final`	No
`payment_methods`	No
`activation_trigger`	No	first_connection (anywhere on the route)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description explains the customer-facing handoff: it returns a buy_url, final price, and ready-to-send checkout block; the customer pays on the route-builder page; no account is needed; and eSIM delivery happens on screen and by e-mail after payment. This adds substantial context about what invoking the tool does and does not handle.

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 description is front-loaded with the key usage condition and alternative routing. It is somewhat long, but the extra statements about delivery, account requirements, and exclusions are operationally useful rather than filler.

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?

Given the annotations, full schema coverage, and an output schema, the description covers the decision context, alternative tool, customer handoff behavior, delivery expectations, and exclusions. An agent has enough information to select and invoke it correctly.

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 the schema already documents all six parameters. The description adds only that the input matches quote_route, which is a useful cross-reference but not additional parameter semantics beyond the structured 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?

The description states a specific action and resource: the checkout handoff for one route, returning a buy_url, final price, and checkout block. It explicitly distinguishes this from quote_route, so an agent can tell the two apart without opening the 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 explicit timing and customer intent examples ('I'll take it', 'how do I buy?') and names the alternative quote_route for comparison pricing. It also states exclusions such as no in-chat order tracking and no discount codes.

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

All variotrip route eSIM configurator tools Inspect

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

Need Help?