Skip to main content
Glama

OsmO Travel eSIM

Get eSIM setup steps

get_esim_setup_steps
Read-onlyIdempotent

Use this when the user needs to install, activate, top up or fix a travel eSIM on iPhone or Android, for example no internet after landing. Gives general phone steps and provider top-up steps where we have them; not provider account support.

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": {
      "platform": "<platform>",
      "stage": "<stage>"
    },
    "name": "get_esim_setup_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageYes
planIdNo
symptomNo
platformYes
providerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavioral context: the answer is generic phone-side guidance with provider top-up steps only 'where we have them', which sets a coverage expectation, and it explicitly declines account-level support.

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 dense sentences with zero filler: the trigger and platforms come first, then the content scope and the exclusion. Nothing is repeated from the schema or annotations.

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

Completeness3/5

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

For a five-parameter retrieval tool with no output schema, the description says what kind of content comes back, which is helpful. It leaves gaps on how planId and provider should be supplied and when symptom is expected versus optional, so an agent may under- or over-populate those fields.

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 0%, so the description must carry parameter meaning. It effectively maps platform ('iPhone or Android'), the four stages ('install, activate, top up or fix'), and the symptom example ('no internet after landing'), but it never mentions planId and only gestures at provider. Two of five parameters remain semantically unexplained.

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 resource with clear scope: it returns eSIM install/activate/top-up/troubleshooting steps for iPhone or Android. The scope boundary 'general phone steps and provider top-up steps... not provider account support' distinguishes it from a support-account tool, though no sibling is named explicitly.

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?

Opens with an explicit trigger ('Use this when the user needs to install, activate, top up or fix a travel eSIM') and gives a concrete example scenario ('no internet after landing'). It also names one exclusion (provider account support), but offers no guidance on when to prefer a browsing/comparison sibling instead.

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.

Resources