IbiPoint eSIM Catalog

Start secure checkout

start_checkout

Read-onlyIdempotent

Hand the customer to the IbiPoint shop to buy one plan. Returns buy_url (the product page where they tap Buy now and pay securely — card, Apple Pay, Google Pay, PayPal, with an optional discount code) plus the plan name and price in the customer's bucket or currency. No account needed; the eSIM is emailed right after payment. There is no in-chat order tracking.

Input Schema

TableJSON Schema

Name	Required	Description
`days`	No	Unlimited Flex only: the duration the customer wants; the returned total_for_days is the checkout total for it.
`bucket`	No	Optional language-region bucket the customer shops in, e.g. "en-gb", "de-de". Wins over language; prices and links are quoted in it.
`currency`	No	Optional ISO 4217 code. Every price in the result is quoted in it.
`language`	No	ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare "en" is quoted in en-us / USD.
`product_id`	Yes	Product id to buy.

Output Schema

TableJSON Schema

Name	Required	Description
`days`	No
`price`	No	Read WITH price_basis.
`buy_url`	No	The exact product page to send the customer to. Use verbatim.
`message`	No
`product`	No
`currency`	No
`app_links`	No	Optional store links of the free IbiPoint app (android, ios) - the eSIM works without it.
`price_max`	No
`days_range`	No
`product_id`	No
`price_basis`	No
`presentation`	No
`price_30_days`	No	Unlimited Flex: price for 30 days, discount applied.
`price_is_final`	No
`pricing_bucket`	No
`total_for_days`	No	Unlimited Flex: checkout total for the requested days, discount applied.

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedSep 29, 2026

addedInput schema / properties / bucket

Added value: +{
+  "description": "Optional language-region bucket the customer shops in, e.g. \"en-gb\", \"de-de\". Wins over language; prices and links are quoted in it.",
+  "type": "string"
+}

addedInput schema / properties / currency

Added value: +{
+  "description": "Optional ISO 4217 code. Every price in the result is quoted in it.",
+  "type": "string"
+}

addedInput schema / properties / days

Added value: +{
+  "description": "Unlimited Flex only: the duration the customer wants; the returned total_for_days is the checkout total for it.",
+  "minimum": 1,
+  "type": "integer"
+}

changedInput schema / properties / language / description

Previous value: -"ISO language of the conversation. Sets the language/currency of the payment page."New value: +"ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare \"en\" is quoted in en-us / USD."

changedInput schema / properties / product_id / description

Previous value: -"WooCommerce product id to buy."New value: +"Product id to buy."

addedOutput schema / properties / app_links / additionalProperties
```
Added value: +true
```

changedOutput schema / properties / app_links / description

Previous value: -"Optional links to the free IbiPoint app (android/ios). Mention only when present."New value: +"Optional store links of the free IbiPoint app (android, ios) - the eSIM works without it."

addedOutput schema / properties / days
```
Added value: +{
+  "type": "integer"
+}
```

removedOutput schema / properties / days_range / description

Removed value: -"Only on price_basis \"per_day\": choosable durations in days, e.g. \"1-365\"."

addedOutput schema / properties / presentation
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / price / description

Previous value: -"Price in currency, to be read WITH price_basis: the full fixed price when \"total\", the price of one day when \"per_day\"."New value: +"Read WITH price_basis."

changedOutput schema / properties / price_30_days / description

Previous value: -"Only on price_basis \"per_day\": price for 30 days, discount applied — the reference figure for a month."New value: +"Unlimited Flex: price for 30 days, discount applied."

removedOutput schema / properties / price_basis / description

Removed value: -"What `price` means for this product. See the plan schema."

addedOutput schema / properties / price_is_final
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / price_max / description

Removed value: -"Only on price_basis \"per_day\": price for the longest duration, discount applied."

addedOutput schema / properties / pricing_bucket
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / product_id
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / total_for_days

Added value: +{
+  "description": "Unlimited Flex: checkout total for the requested days, discount applied.",
+  "type": "number"
+}

Changed5 schema fields changedSep 22, 2026

addedOutput schema / properties / days_range

Added value: +{
+  "description": "Only on price_basis \"per_day\": choosable durations in days, e.g. \"1-365\".",
+  "type": "string"
+}

changedOutput schema / properties / price / description

Previous value: -"Full fixed price in currency; not per-day."New value: +"Price in currency, to be read WITH price_basis: the full fixed price when \"total\", the price of one day when \"per_day\"."

addedOutput schema / properties / price_30_days

Added value: +{
+  "description": "Only on price_basis \"per_day\": price for 30 days, discount applied — the reference figure for a month.",
+  "type": "number"
+}

addedOutput schema / properties / price_basis

Added value: +{
+  "description": "What `price` means for this product. See the plan schema.",
+  "enum": [
+    "total",
+    "per_day"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / price_max

Added value: +{
+  "description": "Only on price_basis \"per_day\": price for the longest duration, discount applied.",
+  "type": "number"
+}

First observedSep 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, openWorldHint=true, destructiveHint=false), and the description does not contradict them — it clarifies that the actual purchase happens off-platform at the returned URL. It adds real context beyond annotations: accepted payment methods (card, Apple Pay, Google Pay, PayPal), optional discount code, no-account requirement, eSIM emailed post-payment, and the absence of in-chat order tracking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and return value in the first clause, then supporting detail. The sentences are dense and purposeful, though the trailing 'There is no in-chat order tracking' is a slightly loose add-on rather than a load-bearing constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't enumerate return fields, yet it still names buy_url and the price/plan-name fields, which is enough orientation. Combined with full schema coverage and annotations, an agent has what it needs; only explicit sibling routing is missing.

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 baseline is 3. The description reinforces the bucket/currency effect on returned prices and mentions the returned total_for_days for Unlimited Flex, but it adds no syntax, defaults, or edge cases that the parameter descriptions don't already carry.

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?

States a specific verb and resource ('Hand the customer to the IbiPoint shop to buy one plan') and immediately names what it produces ('Returns buy_url ... plus the plan name and price'). No sibling could be confused for this: search_esim_plans, recommend_plan, and get_plan_details are all pre-purchase lookups, while this is the single checkout hand-off.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: 'Hand the customer to the IbiPoint shop to buy one plan' tells the agent this is the purchase step, but there is no explicit when-to-use rule, no prerequisite ordering relative to recommend_plan or get_plan_details, and no alternative named. 'No account needed' and 'no in-chat order tracking' hint at scope but don't route the agent.

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

All IbiPoint eSIM Catalog tools Inspect

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

Need Help?