Tripuck

Tripuck eSIM Data Plans

search_esim

Read-onlyIdempotent

Tripuck eSIM search — prepaid travel data plans (eSIM) for a destination country, compared across multiple providers. Use this when the user asks about mobile data, internet, SIM or eSIM for a trip, e.g. "eSIM for Japan", "data plan for my trip to the US", "internet in Dubai", "Japonya için eSIM", "خطة بيانات لدبي", "Datentarif für die Türkei". Input: a destination country (the LLM maps the place to its ISO country code), with optional minimum data (GB), validity days and sorting. Returns available packages with data amount, validity, coverage and price, each deep-linking to Tripuck.com for purchase. The LLM MUST infer the user language from the conversation and pass it via the locale parameter ("tr" Turkish, "en" English, "ar" Arabic, "az" Azerbaijani, "de" German, "ka" Georgian, "uz" Uzbek). All widget UI text and the text response are then returned in that language. If currency is not specified, a sensible default is picked from the locale (tr→TRY, en→USD, de→EUR, ar→USD, az→AZN, ka→GEL, uz→UZS).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`locale`	No	User language as BCP-47 or 2-letter code. Supported: "tr" Turkish, "en" English, "ar" Arabic, "az" Azerbaijani, "de" German, "ka" Georgian, "uz" Uzbek. The LLM MUST infer this from the conversation and pass it explicitly; widget UI and response text will be rendered in this language.
`sortBy`	No	Result ordering: "price_asc" cheapest first (default), "price_desc" most expensive first, "data_desc" largest data first, "validity_desc" longest validity first.	price_asc
`country`	Yes	Destination country as a 2-letter ISO 3166-1 alpha-2 code. The LLM MUST translate the country/city the user mentions to its ISO code (e.g. "Japan" → JP, "Türkiye" → TR, "the US" → US, "Dubai" → AE, "Paris" → FR).
`maxDays`	No	Maximum validity period in days.
`minDays`	No	Minimum validity period in days.
`currency`	No	ISO 4217 currency code. Examples: TRY, USD, EUR, AZN, GEL, UZS. If omitted, a sensible default is picked from the locale (tr→TRY, en→USD, de→EUR, ar→USD, az→AZN, ka→GEL, uz→UZS).
`minDataGb`	No	Minimum data allowance in GB (e.g. 5 for "at least 5 GB").

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses that results deep-link to Tripuck.com for purchase, and explains how locale and currency defaults affect the UI and response language. These details add meaningful operational context without contradicting 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.

Conciseness5/5

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

The description is long but efficient: each sentence contributes either purpose, usage triggers, parameter context, or localization behavior. It is front-loaded with the core purpose and then flows naturally into operational details, 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?

Although there is no output schema, the description clearly states what the tool returns (packages with data amount, validity, coverage, price, deep links) and explains the localization and currency fallback behavior. For a search tool with no nested objects, this is thorough and leaves few open questions for the agent.

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?

The input schema already provides exhaustive descriptions for all 7 parameters, including locale inference, ISO country mapping, sort options, and currency defaults. The description mostly restates the same information rather than adding new meaning, so it meets the baseline for 100% schema coverage but does not exceed it.

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 opens with 'Tripuck eSIM search — prepaid travel data plans (eSIM) for a destination country, compared across multiple providers', which is a specific verb+resource+scope statement. It clearly distinguishes this tool from sibling flight/hotel/meeting-point tools by focusing on eSIM data plans.

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 explicitly says 'Use this when the user asks about mobile data, internet, SIM or eSIM for a trip' and provides concrete query examples in multiple languages. This gives the agent clear, actionable triggers for when to select this tool over others.

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

All Tripuck tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool targets a distinct travel need: flight search, hotel search, eSIM search, price calendar, popular routes, meeting point coordination, and flight details. No two tools overlap in their core function; even cheapest_dates vs search_flights are clearly separated by use case (flexible date overview vs specific trip search).

Naming Consistency4/5

All tool names use lowercase snake_case and are reasonably descriptive. There is a mix of verb-first (search_flights, search_hotels, search_esim, find_meeting_point) and noun/adjective-first (cheapest_dates, popular_routes, flight_details), but the pattern is consistent enough that an agent can predict naming conventions.

Tool Count5/5

Seven tools is well-scoped for a travel search server. Each tool serves a distinct and valuable purpose, covering flights, hotels, eSIM, inspiration, and group coordination without bloat or redundancy.

Completeness4/5

The tool surface covers the core travel search lifecycle: search flights, search hotels, search eSIM, plus helpful extras like cheapest dates and popular routes. Minor gaps exist—for example, no hotel details tool or car rental search—but these are not fatal for the server's primary search-driven purpose.

Resources

Need Help?