Skip to main content
Glama

OsmO Travel eSIM

Keep your number while abroad

get_keep_your_number_guide
Read-onlyIdempotent

Use this when the user asks whether they keep their phone number, WhatsApp, iMessage or bank text codes while using a travel eSIM, or how to set up two SIMs so they aren't charged for roaming data.

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

Input Schema

NameRequiredDescriptionDefault
platformYes
destinationNo
homeCarrierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that this is an explanatory/guide response rather than a lookup of a single value, but it says nothing about response shape, whether answers are platform-specific, or how the destination/carrier inputs affect the answer.

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?

A single sentence, front-loaded with a usage trigger and packed with concrete user phrasings. Nothing is redundant and nothing could be cut without losing routing signal.

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 simple read-only guide tool with no output schema, the question coverage is good, but the definition leaves two real gaps: it never explains the required platform parameter or the optional destination/homeCarrier inputs, and it gives no cue for choosing between it and show_keep_your_number.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, and the description mentions none of them — not that platform is required (ios/android), nor what destination or homeCarrier change about the answer. Since the schema carries no descriptions, the description needed to compensate and does not.

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?

The description states the concrete question space the tool answers (keeping your number, WhatsApp, iMessage, bank SMS codes with a travel eSIM, and dual-SIM setup to avoid roaming charges), which is more informative than the title alone. It does not, however, distinguish this from the sibling show_keep_your_number, whose name suggests overlapping content.

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 opens with an explicit trigger: 'Use this when the user asks whether...' and enumerates the user intents that qualify. There is no when-not guidance and no named alternative for adjacent questions (e.g., setup steps or destination guidance), so it stops short of full routing.

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