Gitsim Chat

Search eSIM Packages

search_packages

Read-only

Search for eSIM data packages by country. Returns up to 10 packages per page sorted by price. Use the page parameter to paginate. No auth required. Call get_business_context first to understand IP routing and package types.

Package types:

"regular": Fixed data pool (e.g. 3GB for 30 days). Best for most travelers.
"daily": Data resets each day (e.g. 2GB/day for 5 days). Good for short trips with predictable daily usage. Top-up days are available.

IP routing (important for Asia):

"breakout": Local IP in destination country. Best for streaming, banking, social media. ALWAYS recommend by default.
"hk": Hong Kong IP. Cheapest but TikTok app and Facebook app are BLOCKED.
"nonhk": Third-country IP (UK, Singapore). No HK restrictions but IP won't match destination.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Case-insensitive substring match on package name
`page`	No	Page number (1-based, default 1). Each page returns up to 10 results.
`type`	No	"daily" = data resets each day (e.g. 2GB/day for 5 days, can top-up days). "regular" = fixed data pool for the full duration. Omit for both.
`country`	Yes	ISO 3166-1 alpha-2 country code, e.g. JP, TH, US
`ip_route`	No	Filter by IP routing type. "breakout" = local IP (recommended default), "hk" = Hong Kong IP (restricted, cheapest), "nonhk" = other breakout (no HK restrictions)
`is_regional`	No	true = only multi-country/regional packages (e.g. Europe, Asia). false = only single-country packages. Omit for both.
`max_data_gb`	No	Maximum data in GB. For daily packages this is the per-day amount.
`min_data_gb`	No	Minimum data in GB. For daily packages this is the per-day amount.
`max_duration_days`	No	Maximum duration in days
`min_duration_days`	No	Minimum duration in days

TDQS

A4.4/5.0

Behavior5/5

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

The description not only aligns with the readOnlyHint annotation (search is read-only) but also adds significant behavioral context: it states 'No auth required', explains package types and IP routing behaviors, and mentions sorting by price. This goes well beyond what annotations alone provide.

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

Conciseness4/5

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

The description is well-structured with sections and bullet points, making it easy to scan. It is fairly long due to the necessary detail, but every sentence adds value. It could be slightly more concise, but the structure compensates.

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 the complexity (10 parameters, no output schema), the description covers key aspects: sorting, pagination, package types, IP routing, and a prerequisite. It lacks details about error handling or rate limits, but overall it provides enough context for effective use.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds substantial meaning beyond the schema. It explains the practical implications of package types (e.g., daily with top-up) and IP routing (e.g., 'hk' blocks TikTok). These details are critical for correct parameter selection and are not present in the schema descriptions.

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 clearly states the tool searches for eSIM data packages by country. It specifies it returns up to 10 packages per page sorted by price. However, it does not explicitly differentiate from the sibling tool search_topup_packages, though the focus on 'eSIM data packages' implies a distinction.

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?

The description advises calling get_business_context first and explains package types and IP routing in detail. This provides context for when to use the tool. It does not explicitly state when not to use it or offer alternatives, but the guidance is clear and helpful.

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

All Gitsim Chat 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.1/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: buying top-ups, checking balances, checking order status, creating orders, getting business context, fetching package details, listing eSIMs, searching packages, and searching top-up packages. No overlapping functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case. Verbs like 'get', 'list', 'search', 'create', 'buy', 'check' are used appropriately, making the naming predictable.

Tool Count5/5

With 9 tools, the server is well-scoped for managing eSIMs. It covers browsing packages, ordering, checking status and balance, listing eSIMs, and handling top-ups without being overwhelming.

Completeness4/5

The tool set covers the main lifecycle: search, create order, check order status, list eSIMs, check balance, and top-up. Missing features like cancellation or order history are minor gaps, but the core workflows are well-supported.

Resources

Need Help?