Skip to main content
Glama

MeiSIM USA

Start a top-up

topup_start

Start a top-up/recharge for an existing line or eSIM, using a product_id from topup_lookup. Returns an order_id and a payment URL where the customer completes payment. For range plans, pass custom_amount.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "line_type": "<line_type>",
      "product_id": "<product_id>",
      "customer_email": "<customer_email>"
    },
    "name": "topup_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
iccidNoeSIM ICCID (esim).
phoneNoUS phone (us_prepaid).
carrierNo
line_typeYes
product_idYesTop-up plan id from topup_lookup.
custom_amountNoFor range/RTR plans only.
customer_emailYes
source_order_idNoOriginal eSIM order id (esim).

Output Schema

NameRequiredDescriptionDefault
errorNo
amountYes
statusYes
messageNo
productNo
currencyYes
order_idYes
payment_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the basic safety profile is covered. The description adds meaningful behavioral context: it returns an order_id and a payment URL where the customer completes payment, clarifying that this starts a payment flow rather than completing a charge. It does not cover idempotency or what happens if payment is never completed, which keeps it from being a 5.

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?

Three compact sentences, front-loaded with the action and prerequisite, followed by the return behavior and the custom_amount rule. Every sentence adds useful information with no redundant wording.

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?

For an 8-parameter mutation with an output schema, the description covers the core workflow, the lookup prerequisite, the payment URL return, and the custom_amount case. It leaves some parameter-specific identification details to the schema, but overall it is complete enough for an agent to select and invoke the tool 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 63%, and the schema already documents product_id as coming from topup_lookup and custom_amount as for range/RTR plans, so the description largely repeats those points. It connects 'existing line or eSIM' to line_type implicitly but does not explain carrier, customer_email, or source_order_id beyond the schema. Baseline 3 is appropriate for this coverage level.

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: starting a top-up/recharge for an existing line or eSIM. It also names topup_lookup as the source of product_id, which separates lookup from execution and distinguishes it from that sibling.

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?

It gives clear usage context by requiring product_id from topup_lookup and by saying custom_amount is for range plans. It does not explicitly state exclusions such as when not to use this versus purchasing a new eSIM, so it falls short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.