Skip to main content
Glama

Hungry eSIM

by com.hungry-esim
OverviewDiscussionsAdmin

Search eSIM plans

search_esim_plans
Read-only

Search prepaid travel eSIM data plans for a destination — the SIM card / mobile data / roaming option for a trip. Use this first for any "data plan for my trip to X" request. Includes unlimited plans where the traveller picks the number of days, and fixed-data plans. Filter by unlimited vs fixed-data, minimum data, and validity. Unlimited plans are quoted per day, fixed-data plans as a one-off total — never compare those two numbers directly. The unlimited total is the per-day price × days, with a volume discount from 7 days, so pass days (trip length) to get that total quoted alongside the daily rate. Price differences between similar plans come from the routing IP country (routing_ip_country) and the supported networks (speed) — quote both when comparing plans. Results are grouped: fixed-data plans first, then unlimited; each group sorted by price. Returns variant_id values to pass to create_checkout.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoTrip length in days (1-90; each unlimited plan states its own maximum). When given, unlimited plans also quote the total for that many days.
limitNoMax results, default 10
countryYesISO 3166-1 alpha-2 country code, e.g. 'JP', 'US'
currencyNoISO currency for prices, default USD
unlimitedNoIf set, return only unlimited (true) or only fixed-data (false) plans
min_data_gbNoMinimum data in GB (fixed-data plans)
max_validity_daysNoMaximum validity in days (fixed-data plans)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / days / description
      Previous value: -"Trip length in days (1-30, the range an unlimited plan can be bought for). When given, unlimited plans also quote the total for that many days, multi-day discount included."New value: +"Trip length in days (1-90; each unlimited plan states its own maximum). When given, unlimited plans also quote the total for that many days."
    • changedInput schema / properties / days / maximum
      Previous value: -30New value: +90
  2. Changed1 schema field changed
    • addedInput schema / properties / days
      Added value: +{
+  "description": "Trip length in days (1-30, the range an unlimited plan can be bought for). When given, unlimited plans also quote the total for that many days, multi-day discount included.",
+  "maximum": 30,
+  "minimum": 1,
+  "type": "integer"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations with pricing behavior that fundamentally affects how results must be read: unlimited plans quoted per day vs fixed-data as a one-off total, an explicit warning never to compare those numbers directly, and the volume-discount rule from 7 days. It also discloses result ordering (fixed-data first, then unlimited, sorted by price) and that outputs carry variant_id for create_checkout.

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?

Front-loads the core purpose and entry-point rule, then spends its remaining sentences on non-obvious pricing semantics and return routing. Dense but every sentence carries decision-relevant information with 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?

There is no output schema, and the description compensates by describing result grouping, sort order, and the variant_id handoff to create_checkout. Combined with the pricing caveats, an agent has everything needed to call it and interpret the response correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema: that days is trip length used to quote an unlimited total (per-day price × days, with discount from 7 days), that unlimited toggles between the two plan families, and that routing_ip_country and supported networks explain price differences between similar plans.

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?

States a specific verb+resource ("Search prepaid travel eSIM data plans for a destination") and clarifies the domain equivalent (SIM card / mobile data / roaming option for a trip). It routes the agent with "use this first for any 'data plan for my trip to X' request," but never explicitly distinguishes itself from the sibling find_cheapest_plan or get_plan_details, which overlap heavily.

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?

"Use this first for any 'data plan for my trip to X' request" gives a clear entry-point condition, and the filtering description implies when to use the unlimited/min_data_gb/max_validity_days filters. However, no when-NOT-to-use guidance and the cheaper/more specific siblings (find_cheapest_plan, get_plan_details) are never named as alternatives.

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

All Hungry eSIM 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