Skip to main content
Glama

OsmO Travel eSIM

Check phone eSIM support

check_esim_device
Read-onlyIdempotent

Use this when the user asks whether their phone, tablet or watch supports eSIM. Answers from a maintained list of manufacturer-published specs; returns 'unknown' with self-check steps for models not listed.

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": {
      "deviceModel": "<deviceModel>"
    },
    "name": "check_esim_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceModelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so safety needs no restating. The description adds genuinely new behavior: the answer comes from a maintained list of manufacturer-published specs, and unlisted models yield 'unknown' plus self-check steps, which tells the agent how to handle a miss.

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, zero filler, with the trigger condition front-loaded before the behavioral detail. Every clause earns its place.

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 a one-parameter lookup with no output schema, the description covers source of truth, scope of supported devices, and the fallback result for unknown models. The only real omission is input-format guidance for deviceModel, which the bare schema does not supply either.

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 0% for the single required deviceModel parameter, so the description must carry the load. It implies the input is a device model and that unlisted models are possible, but never says what format to pass (marketing name vs. model number) despite an 80-character limit and no enum, leaving the agent to guess.

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 a specific resource and question type: whether a phone, tablet or watch supports eSIM, answered from manufacturer-published specs. That is clearly distinct from plan-comparison and setup-step siblings, 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?

It gives an explicit trigger condition ("Use this when the user asks whether their phone, tablet or watch supports eSIM"), which is a clear when-to-use rule. It stops short of naming when-not to use it or pointing to adjacent tools such as get_esim_setup_steps once support is confirmed.

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