Skip to main content
Glama

Siima eSIM

by online.siima
OverviewDiscussionsAdmin

Create eSIM checkout link

create_checkout_link

Create a secure payment link on siima.online for a Siima eSIM plan (Stripe-powered, but hosted on our own site — never a redirect to checkout.stripe.com). Give the returned url to the user to complete payment. Optionally pass the buyer's email to pre-fill the checkout form. The buyer confirms it with a 6-digit code we email them, then pays — nothing is ordered until they do. After payment, the eSIM QR code, one-tap activation link, and manual installation codes are emailed to the buyer within a minute. No account or signup is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoBuyer email to pre-fill at checkout (they verify it before paying; the eSIM is delivered there)
plan_idYesPlan id from search_esim_plans
currencyNoCurrency for prices: "usd", "eur", or "gbp". Defaults to "usd".usd

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"Buyer email to pre-fill at checkout (eSIM is delivered to this address)"New value: +"Buyer email to pre-fill at checkout (they verify it before paying; the eSIM is delivered there)"
  2. Changed1 schema field changed
    • addedInput schema / properties / currency
      Added value: +{
+  "default": "usd",
+  "description": "Currency for prices: \"usd\", \"eur\", or \"gbp\". Defaults to \"usd\".",
+  "enum": [
+    "usd",
+    "eur",
+    "gbp"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it does so thoroughly: it discloses the Stripe-backed but self-hosted payment flow, the email verification step, the fact that nothing is ordered until the buyer confirms and pays, and post-payment email delivery. It also notes that no account or signup is required.

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 front-loaded with the core action and immediate next step, then adds necessary workflow details. Every sentence earns its place, and the parenthetical about not redirecting to checkout.stripe.com is useful and compact.

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 checkout-link creation tool with no output schema and no annotations, the description is remarkably complete: it covers what the tool creates, how the buyer flow works, what is delivered after payment, and the no-signup requirement. Nothing essential is missing for an agent to call it 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 description coverage is 100%, so the schema already documents all three parameters. The description adds mild context for the email parameter ('pre-fill the checkout form') and references plan_id indirectly, but it does not meaningfully extend beyond the schema.

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 secure payment link on siima.online for a Siima eSIM plan. It is clearly distinguished from sibling read/search tools like search_esim_plans and get_esim_plan, and it explains what to do with the returned URL.

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 makes clear this tool is for generating a payment link that the user completes, and that it is the action-oriented counterpart to the plan-lookup siblings. It gives context for use but does not explicitly state when not to use it or name alternative tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Siima eSIM 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