Skip to main content
Glama

MeiSIM USA

Look up a line to top up

topup_lookup
Read-only

Look up an existing US prepaid line (by phone) or an eSIM (by ICCID / order) and list the top-up plans available for it. Returns product_ids to pass to topup_start.

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>"
    },
    "name": "topup_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoCustomer email (required for esim lookup).
iccidNoeSIM ICCID (for esim).
phoneNoUS phone number (for us_prepaid).
carrierNoCarrier name/id (for us_prepaid; see topup carriers).
line_typeYes"us_prepaid" for a US phone line, "esim" for a travel eSIM.

Output Schema

NameRequiredDescriptionDefault
hintNo
linesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful workflow fact that results feed topup_start, but says nothing about failure modes (unknown line, wrong email for eSIM), permissions, or rate limits, which matters for an openWorldHint lookup.

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 sentences with no filler; the resource scope and the two lookup paths come first, and the output/handoff fact comes second. Nothing is repeated and nothing needs to be skimmed past.

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 not be explained, and the description correctly focuses on what to call and what to do next. It is nearly complete for a 5-parameter read tool, with the only real gap being what the agent should expect or do when a lookup returns no match.

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 every parameter (email, iccid, phone, carrier, line_type) is already documented in the schema, including which field belongs to which line_type. The description restates the same phone-vs-ICCID split without adding format or validation detail, so baseline 3 applies.

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 (look up) and two concrete resources (US prepaid line by phone, eSIM by ICCID/order), then names the additional output: the available top-up plans. It also names the sibling it feeds (topup_start), so an agent can tell this apart from the purchase tool without opening either schema.

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 phrase "Returns product_ids to pass to topup_start" makes the intended sequence explicit: call this first, then topup_start with the returned ids. There is no explicit when-not guidance (e.g., what to do if the line is not found, or when to prefer get_order over the ICCID path), so it stops short of a 5.

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.