PikaSim

rent_sms_number

Destructive

Rent a LONG-TERM receive-only SMS number: the user keeps the same number for the whole rental and can receive multiple SMS (fair-use 25/day). This SPENDS the wallet balance. Use list_sms_rentals first for rentalId, valid day tiers, prices, and live stock (do not order an OUT OF STOCK tier). Extendable before expiry with extend_sms_rental, and cancellable for a full refund with cancel_sms_rental within 2 hours if no messages arrived. Not allowed for banking/financial/crypto-exchange verification. Requires a connected agent wallet.

Input Schema

TableJSON Schema

Name	Required	Description
`days`	Yes	Rental duration in days — must be one of the duration tiers list_sms_rentals shows for this rentalId
`rentalId`	Yes	The rentalId from list_sms_rentals (e.g. 11 for United States)
`requestId`	No	Idempotency key: generate a fresh UUID for each NEW rental, and reuse the SAME value when retrying after a timeout or transport error — an identical retry returns the original rental instead of charging again.

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnly=false, destructiveHint=true, idempotentHint=false), the description discloses that it spends wallet balance, has fair-use limits (25/day), supports full refund within 2 hours if no messages arrived, and is extendable. This adds meaningful operational context without contradicting any annotation.

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 dense yet well-structured: it front-loads the core purpose, then covers cost, prerequisites, lifecycle, restrictions, and requirements. Every sentence adds essential information with no filler or repetition.

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?

Given the tool's complexity (rental mechanics, idempotency, stock dependency, refund policy, forbidden uses) and the absence of an output schema, the description covers all critical operational aspects. It informs the agent of prerequisites, edge cases, and constraints sufficiently for correct invocation.

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 documents all three parameters at 100% coverage, including source of rentalId and the idempotency semantics of requestId. The description reinforces the tie to list_sms_rentals tiers and stock but does not significantly extend beyond schema descriptions, so the 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 opens with a specific verb and resource: 'Rent a LONG-TERM receive-only SMS number,' clearly distinguishing this from sibling tools like order_sms_verification or purchase_esim. It further clarifies the rental keeps the same number and allows multiple SMS, making the scope unmistakable.

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?

Provides explicit when-to-use guidance: call list_sms_rentals first for rentalId, day tiers, prices, and stock, and avoid out-of-stock tiers. Names lifecycle alternatives (extend_sms_rental, cancel_sms_rental) and states restrictions (not for banking/financial/crypto; requires connected wallet), exceeding basic usage instructions.

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?