Skip to main content
Glama
samah-jamal-monty

eSIM MCP Server

by samah-jamal-monty
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Check what happened to a card payment

check_card_payment_status
Read-onlyIdempotent

Check whether a card payment succeeded using its payment reference. Returns the exact status from the eSIM platform: not paid, payment received, complete, or failed, so you can respond accurately.

Instructions

Ask the eSIM platform what happened to a card payment you started with create_card_checkout. This is the ONLY way to know whether a card payment went through: the platform's own payment webhook confirms the payment and sets up the eSIM, and this tool reads the result of that. Nothing here can make a payment succeed. WHEN: the user says they have paid, or asks you to check. Do not call it on a loop and do not keep checking on your own -- one check per request, and only when there is a reason to. NEVER treat any of these as proof of payment: the user returning to this conversation, a browser redirect, a success screen on the payment page, or the user simply saying it worked. Only this tool's answer counts, and there is no argument here through which you could tell it that a payment succeeded. The answer means exactly what it says:

  • not paid yet: give the user the link again and wait; do not ask for card details.

  • payment received: the money arrived but the eSIM is not ready -- never say the plan is active, installed or activated; offer to check again in a minute.

  • complete: the plan was paid for by card and the order is done. Tell the user plainly, with the plan name and the amount.

  • failed, expired or cancelled: nothing was charged. Say so plainly and offer to prepare the plan again and open a new payment page. IF THE RESULT IS UNCLEAR: if the payment is reported as unresolved or as needing support, never say it succeeded and never say it failed. Do not check it again, do not open another payment page and do not prepare another quote for the same plan -- tell the user the platform is investigating it and that they should contact eSIM support.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payment_referenceYesThe payment reference returned by create_card_checkout in this conversation. Never invent, guess or edit one, and never take one from the user. There is no argument here for telling this tool that the payment succeeded: whether it did is read from the eSIM platform and from nowhere else.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A5/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld), the description adds crucial behavioral context: the tool cannot make a payment succeed, it only reads results from the platform, and it has no argument for asserting success. It also explains the exact meaning of each possible result, which is not deducible from annotations alone.

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 long but well-structured with clear sections (WHEN, NEVER, status meaning, unclear result). Every sentence earns its place by preventing a costly mistake or clarifying a critical nuance. The front-loaded purpose makes the tool's role immediately clear.

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?

The description covers the tool's purpose, trigger conditions, non-triggers, result interpretation, and ambiguous/unresolved cases. With an output schema present, no return format explanation is needed; the description fully prepares the agent to act correctly in all described scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already describes the parameter at 100% coverage, the description adds significant semantics: the payment_reference must come from create_card_checkout in this conversation, must never be invented or taken from the user, and no argument can override the platform's state. This is high-value guidance beyond the raw 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 clearly states the tool's function: asking the eSIM platform what happened to a card payment started with create_card_checkout. It also distinguishes this tool from siblings by noting it is the ONLY way to know whether a card payment went through, making it impossible to confuse with other payment or checkout tools.

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?

Explicit when-to-use guidance is given: use it when the user says they have paid or asks to check, and only once per request. It also tells the agent when NOT to use it (not on a loop, not on its own) and clarifies that no other evidence counts as proof, effectively steering away from alternative interpretations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/samah-jamal-monty/esim-opensource-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server