variotrip route eSIM configurator

Networks of a country

get_networks

Read-onlyIdempotent

The mobile networks the customer can tick for one country (operator name, 4G/5G) with the price of a reference one-country route with that network switched on (1 GB · 7 days; the networks of the country that are not dearer come with it), so you can say which network is the cheapest and what the others add.

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": "get_networks"
  }
}

Input Schema

Name	Required	Description
`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.
`destination`	Yes	Country in ANY language or its ISO code, e.g. "Japan", "Japon", "jp". Map a city to its country first.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuinely non-obvious domain context: prices are for a specific reference route (1 GB · 7 days) and networks not dearer than the reference 'come with it', which an agent could not infer from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single very dense sentence with the purpose front-loaded, and most clauses carry real information. But the phrasing 'the networks of the country that are not dearer come with it' is tangled enough to require re-reading, and the parenthetical pricing model is buried mid-sentence.

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?

There is no output schema, so the description must convey what comes back, and it does name the returned fields (operator name, 4G/5G, reference price). The only gap is that it never states the result is a list of networks or how the price comparison is presented, leaving some inference about shape.

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 destination, language, bucket, and currency are already documented in the schema. The description contributes only the notion that the tool is scoped to 'one country'; it adds nothing about the optional localization/currency parameters, so baseline 3 applies.

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?

The description names the concrete resource and payload: mobile networks a customer can pick for one country, with operator name, 4G/5G flag, and the price of a reference one-country route. It is specific enough to distinguish this lookup from pricing/checkout siblings, but it is delivered as a long noun phrase with no explicit verb and never names a sibling to contrast with.

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

Usage Guidelines3/5

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

The trailing clause 'so you can say which network is the cheapest and what the others add' implies the use case: answering cheapest-network / network-comparison questions. There is no explicit when-not guidance and no pointer to alternatives such as quote_route or price_grid for actual pricing.

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?