Skip to main content
Glama

PikaSim

by com.pikasim
OverviewDiscussionsAdmin

topup_esim

Destructive

Adds more data (and on some plans voice/SMS) to an existing eSIM the user already owns, without issuing a new eSIM. This SPENDS the wallet balance and cannot be undone. First call get_topup_options with the same ICCID to get valid top-up package codes and prices, then pass one here. Use when a user wants to extend an eSIM that is running low rather than buy a new one. Requires a connected agent wallet (OAuth or ak_live_ key).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iccidYesThe ICCID of the eSIM to top up (from list_orders or a prior purchase)
promoCodeNoOptional promo/discount code. Validated server-side; an invalid code rejects the top-up with the reason (nothing is charged). Only pass a code the user explicitly provided.
packageCodeYesA top-up package code returned by get_topup_options for this ICCID (top-up codes differ from new-purchase codes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / promoCode
      Added value: +{
+  "description": "Optional promo/discount code. Validated server-side; an invalid code rejects the top-up with the reason (nothing is charged). Only pass a code the user explicitly provided.",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / iccid / description
      Previous value: -"ICCID of the eSIM to top up"New value: +"The ICCID of the eSIM to top up (from list_orders or a prior purchase)"
    • changedInput schema / properties / packageCode / description
      Previous value: -"Top-up package code"New value: +"A top-up package code returned by get_topup_options for this ICCID (top-up codes differ from new-purchase codes)"
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description adds critical behavioral details beyond the annotations: 'This SPENDS the wallet balance and cannot be undone' specifies the destructive impact, and 'Requires a connected agent wallet (OAuth or ak_live_ key)' adds auth requirements. It also clarifies that no new eSIM is issued, which is a key side-effect distinction.

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?

Five sentences, each essential: purpose, consequence, prerequisite, usage condition, and auth requirement. No fluff; information is front-loaded and well-organized.

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 lacking an output schema, the description covers the action, side effects, prerequisite, usage scenario, and authentication. It also indirectly addresses error conditions via the schema's promoCode note. For a financial mutation tool, this is highly complete.

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 baseline is 3. The description adds the workflow directive 'First call get_topup_options with the same ICCID to get valid top-up package codes and prices, then pass one here', which supplements the packageCode and iccid descriptions in the schema. It provides extra guidance on the relationship between parameters and the prerequisite call, elevating it above 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?

The description clearly states the action: 'Adds more data... to an existing eSIM' and distinguishes it from purchasing a new one ('without issuing a new eSIM', 'rather than buy a new one'). It also differentiates from sibling tools like get_topup_options by specifying the top-up action itself.

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?

Explicitly states when to use: 'Use when a user wants to extend an eSIM that is running low'. Provides a prerequisite and alternative: 'First call get_topup_options with the same ICCID... then pass one here'. The phrase 'rather than buy a new one' implies not using purchase_esim for this purpose.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources