Skip to main content
Glama
Sign In

Slashtel

by com.slashtel
OverviewDiscussionsAdmin

List eSIM destinations

list_esim_destinations
Read-onlyIdempotent

Lists every country and region Slashtel sells travel data eSIMs for (about 200 destinations), returning each destination's code, name, lowest live price in USD and number of plans. Use it to find the destination code when the user names a place, a region such as Europe or Asia, or is unsure what is covered. Optional search text filters by name. Skip this tool and call get_esim_plans directly when you already know the ISO-2 country code.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_esim_destinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoOptional. Part of a country or region name to filter by, e.g. 'turk', 'japan' or 'europe'. Leave empty to list all destinations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / search / description
      Previous value: -"Part of a country or region name, e.g. 'turk' or 'europe'"New value: +"Optional. Part of a country or region name to filter by, e.g. 'turk', 'japan' or 'europe'. Leave empty to list all destinations."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds non-obvious behavior beyond that: the catalog size (~200), that prices are 'live' rather than static, and that each row carries a plan count alongside the price. It stops short of mentioning pagination or result ordering, so it is not a full 5.

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

Conciseness5/5

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

Three tightly packed sentences, front-loaded with what the tool returns before branching into usage and the alternative. Every sentence carries actionable information and there is no 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?

With no output schema, the description carries the return-value burden and does so by listing the four fields returned. Combined with the destination count, the known-code bypass, and the read-only annotations, an agent has everything needed to call this correctly in one shot.

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% and the single `search` parameter is fully documented there, so the baseline is 3. The description's note that empty search lists everything is essentially a restatement of the schema text; it adds no new syntax, matching rules, or case-sensitivity guidance.

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 (list eSIM destinations sold by Slashtel), quantifies scope (~200 destinations), and enumerates the returned fields (code, name, lowest live price in USD, plan count). It also names a sibling (get_esim_plans), so an agent can distinguish the lookup tool from the plan-detail tool 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 triggers (user names a place, a region like Europe or Asia, or is unsure what is covered) and an explicit exclusion plus alternative (skip this and call get_esim_plans directly when the ISO-2 code is already known). Both the when and the when-not are covered.

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

All Slashtel toolsInspect
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