Skip to main content
Glama

Quote a travel eSIM

quote_travel_esim
Read-onlyIdempotent

Find current Simcardo eSIM plans for a dated trip. Use when the traveler needs a plan that covers a destination, trip duration, data allowance or tethering requirement. Return verified matches with total price, activation terms and a direct product link, or explain why no plan can be confirmed.

Input Schema

NameRequiredDescriptionDefault
data_gbNoTotal requested GB for the entire trip; 1 GB = 1000 MB. Provide this OR usage_profile.
currencyYesStorefront currency code, e.g. EUR, USD, JPY, THB or CZK.
end_dateYesLast local calendar day, included (YYYY-MM-DD).
languageNoStorefront language for localized destination names, price display and links. Reply to the traveler in their language.en
start_dateYesFirst local calendar day of coverage (YYYY-MM-DD).
destinationYesUppercase country or territory code, e.g. TH, JP, US, BR. Ask for clarification rather than guessing.
usage_profileNoChoose this when the traveler described usage rather than specifying GB. The catalogue estimates the required GB. Do not send both.
hotspot_requiredNoTrue requires explicit supplier confirmation that tethering is allowed for the exact plan.
include_regionalNoFor a single destination, also consider packages with verified coverage there. Defaults to dedicated country plans only.
additional_destinationsNoAdd other country codes to find one eSIM with verified coverage in every listed country for the full date range.

Output Schema

NameRequiredDescriptionDefault
noteYes
plansYes
statusYes
requestYes
reason_codesYes
destination_urlYes
catalogue_checked_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent, open-world lookup. The description adds behavioral value by saying it returns verified matches with total price, activation terms, and a direct link, or explains why no plan can be confirmed.

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?

The description is three focused sentences: purpose first, usage condition second, and return behavior third. There is no redundant or filler text.

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?

Given ten parameters, a complete schema, and an output schema, the description is largely sufficient for correct invocation. It omits explicit mention of multi-destination or regional-plan options, but those are covered in the structured schema.

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 input schema already documents all ten parameters thoroughly, including the data_gb/usage_profile choice and destination codes. The description only broadly refers to destination, trip duration, data allowance, and tethering, adding little beyond the schema.

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 gives a specific verb and resource: finding current Simcardo eSIM plans for a dated trip. It is clear what the tool does, but it does not explicitly contrast itself with sibling tools like list_esim_plans or list_esim_destinations.

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

Usage Guidelines4/5

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

It states when to use the tool: when the traveler needs a plan covering a destination, trip duration, data allowance, or tethering requirement. It provides clear context but no explicit exclusions or alternative-tool routing.

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