ConnectMeGuru eSim

purchase_esim_with_wallet

Purchases an eSIM package directly in chat using the user's wallet balance. If balance is insufficient, returns a magic link to top-up.

Input Schema

TableJSON Schema

Name	Required	Description
`token`	No	The secure session token returned by verify_agent_otp or a Personal Access Token.
`packageCode`	Yes	The package code of the eSIM (e.g. PIK0SW14Q).
`discountCode`	No	Optional coupon code (e.g. WELCOME10).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`content`	No
`isError`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "content": {
+      "items": {
+        "properties": {
+          "text": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "text"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "isError": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedJul 30, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false mutation, non-idempotent, openWorld). The description adds genuine behavior beyond that: the charge is drawn from wallet balance and, critically, the insufficient-balance path returns a magic top-up link rather than simply failing. That failure-mode disclosure is meaningful and not present in the structured fields.

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?

Two tight sentences, front-loaded with the action and followed by the edge-case outcome. No filler or redundancy.

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?

An output schema exists, so return values need no explanation, and the description still usefully calls out the magic-link fallback. What remains unstated is the permission/token prerequisite and any idempotency implications, though annotations plus the token param cover most of that.

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%, so token, packageCode and discountCode are all documented in the schema with examples; the description adds no additional parameter meaning. Baseline 3 is appropriate when the schema carries the semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Purchases an eSIM package') and the mechanism ('using the user's wallet balance'), which implicitly distinguishes it from siblings like purchase_topup and get_checkout_url. It does not explicitly name or contrast those siblings, so it stops short of a 5.

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?

The phrase 'directly in chat using the user's wallet balance' implies the usage context and differentiates the wallet-payment path, but there is no explicit when-to-use/when-not guidance and no named alternatives such as get_checkout_url or purchase_topup. Adequate but inferential.

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

All ConnectMeGuru eSim 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?