PikaSim

create_wallet

Create a NEW PikaSim agent wallet for autonomous purchasing — no human, no browser, no account, no email, no KYC. Returns a wallet code + an ak_live_ API key + a small spend-only welcome credit, so you can immediately reconnect with the key (Authorization: Bearer ak_live_…) and buy an eSIM, phone number, or SMS verification number. Use this when the user has NO wallet yet and wants their agent to buy. If the user ALREADY has a wallet, do NOT create a new one — reconnect the existing wallet instead (ask them for it). You accept the Terms of Service (https://pikasim.com/tos) on the user's behalf by passing acceptTos=true.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`acceptTos`	Yes	Must be true: confirms the user accepts the PikaSim Terms of Service (https://pikasim.com/tos). Required to create the wallet.

TDQS

A4.6/5.0

Behavior4/5

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

Adds meaningful context beyond annotations: discloses that creating the wallet accepts ToS on the user's behalf, returns a spend-only credit, and requires no KYC/email. Annotations already indicate mutation, but the description enriches with legal and operational details that influence agent behavior.

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 front-loaded with the core purpose and efficiently packs necessary caveats (no human/KYC, what it returns, when to use, ToS). Slightly long, but every sentence adds distinct value without redundancy.

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?

With no output schema, the description fully covers the return value (wallet code, API key, welcome credit), how to authenticate with the key, and what purchases can follow (eSIM, phone number, SMS). It is complete for a create-wallet tool.

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?

Though the schema already describes acceptTos clearly, the description adds the critical behavioral implication: passing true means accepting ToS on the user's behalf. This goes beyond the schema's 'Must be true' and explains why the parameter exists, aiding correct invocation.

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 states a specific verb and resource: 'Create a NEW PikaSim agent wallet for autonomous purchasing.' It clearly distinguishes from siblings by noting when not to use it (if user already has a wallet, reconnect instead) and lists concrete outputs (wallet code, API key, credit).

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?

Explicit usage guidance is provided: 'Use this when the user has NO wallet yet' and 'If the user ALREADY has a wallet, do NOT create a new one — reconnect the existing wallet instead.' This directly tells the agent when to use this tool vs. alternatives.

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?