PikaSim

purchase_phone_plan

Destructive

Purchase a PHONE-NUMBER eSIM — a plan with a real carrier phone number (voice + SMS + data). Deducts from your prepaid agent wallet and returns order details with activation info (ICCID, QR code, SM-DP+). The real phone number is assigned by the carrier when the eSIM registers on the network and appears in the device settings after activation. Use the packageCode from search_phone_plans. Plans whose search result says "designated-date activation" REQUIRE activationDate. Requires an agent-wallet API key (ak_live_).

Input Schema

TableJSON Schema

Name	Required	Description
`promoCode`	No	Optional promo/discount code. Validated server-side; an invalid code rejects the order with the reason (nothing is charged). Only pass a code the user explicitly provided.
`requestId`	No	Idempotency key: generate a fresh UUID for each NEW purchase, and reuse the SAME value when retrying after a timeout or transport error — an identical retry returns the original order instead of charging again.
`packageCode`	Yes	Phone-plan package code (use search_phone_plans to find codes, e.g., change-plus-7days-1gb)
`activationDate`	No	Activation date in YYYY-MM-DD — ONLY for plans marked "designated-date activation" in search results (e.g. the Australia phone plan), where it is REQUIRED and must be at least 2 and at most 60 days from today. Ask the user for their service start date. Omit for all other plans.

TDQS

A4.6/5.0

Behavior5/5

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

The description discloses important behavioral traits beyond the annotations: it deducts from the prepaid agent wallet, requires an ak_live_ API key, and explains that the phone number is assigned later during network registration. This adds significant context beyond destructiveHint and readOnlyHint.

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 dense but efficient, with each sentence adding useful information. It is front-loaded with the core purpose and includes necessary caveats. Slightly long but justified by complexity.

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?

Despite no output schema, the description covers return details (order details with ICCID, QR code, SM-DP+), prerequisites, side effects, and special activation cases. This is thorough for a purchase tool with this complexity.

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 parameters are well-defined. The description adds value by clarifying that packageCode comes from search_phone_plans and that activationDate is required only for specific plans, which is not fully explicit in the schema.

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 identifies the tool as purchasing a PHONE-NUMBER eSIM with voice/SMS/data, distinguishing it from sibling tools like purchase_esim. It uses a specific verb (Purchase) and resource (phone-number eSIM), making its purpose 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?

Provides clear when-to-use context: it instructs to use packageCode from search_phone_plans, warns about designated-date activation plans requiring activationDate, and states the API key requirement. While it doesn't explicitly name alternatives, the context is sufficient for appropriate selection.

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

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

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

Need Help?