Skip to main content
Glama

PikaSim

by com.pikasim

extend_sms_rental

Destructive

Extend a long-term SMS rental so the user keeps the same number — days are ADDED on top of the current expiry. This SPENDS the wallet balance at the live tier price (the tool checks the price first and reports what was charged). Valid day options are the same duration tiers the rental was offered at. Extend BEFORE expiry; an expired rental usually cannot be recovered. Requires a connected agent wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysYesHow many days to add — one of the rental's duration tiers (see list_sms_rentals for this country)
receiptIdYesThe rental receipt ID

TDQS

A4.7/5.0
Behavior5/5

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

Annotations mark destructiveHint=true and readOnlyHint=false; description adds specifics: it spends wallet balance, checks price first, reports charged amount, and days are added to current expiry. This goes beyond annotation hints and gives actionable context.

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?

One tight paragraph, front-loaded with the main purpose. Each sentence contributes critical info: action, cost behavior, time constraint, prerequisite. No filler.

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?

For a 2-param action with no output schema, the description is sufficient. It covers behavior, impact on wallet, prerequisites, and failure warning (expired rentals). Return value not needed as no output schema.

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 already covers both params with descriptions (100% coverage). Description adds context that days are added on top of current expiry and must match duration tiers. Reinforces schema without adding new syntax, so slightly better than baseline.

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?

Specific verb+resource: 'Extend a long-term SMS rental' clearly indicates the action and target. Distinguished from siblings by emphasizing keeping the same number and adding days, unlike cancel or list operations.

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?

Explicitly states when to use: 'Extend BEFORE expiry; an expired rental usually cannot be recovered.' Also provides prerequisites: 'Requires a connected agent wallet.' Does not name alternatives but clearly implies this is for extension only, not cancellation or new rental.

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