Skip to main content
Glama

PikaSim

by com.pikasim

search_esim_packages

Read-only

Search PikaSim eSIM plans by country code, region, or keyword. Returns BOTH product lines in separate buckets: DATA eSIMs and PHONE-NUMBER eSIMs (real carrier number + voice + SMS). Each result shows its packageCode in [brackets] for purchasing. Use type to narrow to one line.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoWhich product line to return: "data" (data-only eSIMs), "phone" (phone-number eSIMs with voice+SMS), or "all" (both, default)
queryNoSearch keyword (e.g., "Japan 10GB")
regionNoRegion name (e.g., Europe, Asia, Global)
countryNoISO 3166-1 alpha-2 country code (e.g., JP, US, DE)

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description doesn't need to restate safety. It adds valuable behavioral details: results are bucketed by product line, packageCode is shown in brackets for purchasing, and the 'type' parameter narrows to one line. This goes beyond what annotations provide.

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 concise sentences, front-loaded with the core purpose. Every sentence earns its place: search criteria, result structure, and narrowing instruction. No fluff or redundancy.

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 this is a read-only search tool with 4 optional parameters and no output schema, the description is complete enough. It explains inputs, return structure (separate buckets), and the packageCode notation needed for purchasing. No critical invocation details are missing.

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 schema already provides detailed descriptions for all four parameters (100% coverage). The description reinforces the search criteria (country, region, keyword) and mentions the 'type' narrowing, but does not add significant new meaning beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool searches PikaSim eSIM plans by country code, region, or keyword, and explicitly distinguishes it from sibling tools by noting it returns BOTH product lines (DATA and PHONE-NUMBER eSIMs) in separate buckets. This makes the purpose specific and unambiguous.

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 provides clear usage context: when searching eSIM plans by various criteria, and how to narrow results using the 'type' parameter. However, it does not explicitly mention alternative tools (e.g., search_phone_plans) or specify when not to use this tool, so it falls short of full exclusion guidance.

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

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

A3.9/5.0
Disambiguation3/5

There is notable overlap between search tools (search, search_esim_packages, search_phone_plans) and detail tools (fetch, get_package_details, get_pricing, get_phone_plan_pricing). While descriptions clarify some differences, agents may struggle to pick the right tool without careful reading, especially between 'search' and 'search_esim_packages' and between 'fetch' and 'get_package_details'.

Naming Consistency4/5

Most tools follow a clear verb_noun convention (e.g., purchase_esim, list_orders, get_balance). A few are single verbs like 'fetch' and 'search', which stand out but are still recognizable as actions. Overall the pattern is predictable and readable.

Tool Count2/5

With 31 tools, this is a large set. The server covers several distinct sub-domains (eSIM data, phone-number eSIM, SMS verification, SMS rentals, wallet management), which justifies some size, but the count is on the high side and could be consolidated (e.g., merging search tools or detail-fetching tools).

Completeness4/5

The tool surface covers the full lifecycle for each product line: search, view details, purchase, list, check status, top-up/cancel, plus wallet management. The only minor gap is a lack of explicit update tools (e.g., changing a phone plan), but core workflows are well supported.

Resources