PikaSim

list_orders

Read-only

Returns the order history for the connected wallet, newest first: each order's ID, package, status, cost, date, ICCID, and install link. Read-only and paginated. Use this to find a past purchase, retrieve an ICCID for get_esim_status, or show a user what they have bought. Results are scoped to this wallet only. Requires a connected agent wallet (OAuth or ak_live_ key).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	1-based page number to retrieve (default 1)
`limit`	No	Number of orders per page (default 20, maximum 50)

TDQS

A4.3/5.0

Behavior4/5

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

Although readOnlyHint is already in annotations, the description adds valuable behavior: pagination, ordering (newest first), wallet-scoping, and authentication requirements. It also indicates what fields the response includes, which is useful given no output schema.

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 two sentences and front-loaded with the core action and return fields. The second sentence adds usage guidance and constraints without fluff. Every sentence earns its place.

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 simple two-parameter schema and read-only annotation, the description provides all necessary context: purpose, return fields, ordering, pagination, scope, auth, and use cases. The lack of an output schema is compensated by listing the returned fields. It is complete enough for an agent to select and invoke correctly.

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?

Schema coverage is 100% with clear descriptions for page and limit. The description adds the word 'paginated' but does not explain parameter semantics beyond what the schema already provides. For a simple pagination setup, 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 'Returns the order history for the connected wallet, newest first' and enumerates the exact fields returned (ID, package, status, cost, date, ICCID, install link). It distinguishes itself from siblings like list_esims and list_transactions by focusing on order history with wallet scoping.

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 explicitly lists concrete use cases: 'find a past purchase, retrieve an ICCID for get_esim_status, or show a user what they have bought.' It also provides important context like wallet-only scoping and auth requirements. However, it does not explicitly state when not to use this tool or mention 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?