Skip to main content
Glama

Check eSIM compatibility

devices_check
Read-only

Check whether a phone or tablet supports eSIM against the compatible-device list simoptions.com publishes, by its model name ("iPhone 15 Pro", "Samsung Galaxy S24") or model code ("SM-S921B"). "yes" names the listed model. "unknown" means it is not on the list, which only holds compatible models: it is not a no, and the phone's settings tell whether it has an eSIM option.

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": {
      "model": "<model>"
    },
    "name": "devices_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesThe phone or tablet: its model name ("iPhone 15 Pro", "Samsung Galaxy S24") or model code ("SM-S921B").

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=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior that annotations cannot convey: the return semantics of 'yes' and 'unknown', the crucial warning that the underlying list contains only compatible models so 'unknown' is not a 'no', and a suggested fallback verification via the phone's settings. It omits nothing harmful, though it does not mention latency or rate limiting.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the verb and resource, followed by the two outcome definitions and the important caveat. It is dense but each sentence carries information. The final sentence is a long chained clause ('which only holds compatible models: it is not a no, and...') that costs some readability.

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?

With no output schema, the description takes on the job of explaining return values, and it does so for 'yes' and 'unknown' plus the interpretive caveat. For a single-parameter read-only lookup this is nearly complete; it stops short of stating the full set of possible return values (whether a distinct negative result exists) or what happens on an unparseable model string.

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%, and the parameter description already spells out model name versus model code. The description repeats the same two example formats ('iPhone 15 Pro', 'SM-S921B') without adding format rules, normalization, or case-sensitivity guidance, so it earns the baseline rather than credit beyond the schema.

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 and resource ('Check whether a phone or tablet supports eSIM') plus the exact data source it validates against (the simoptions.com compatible-device list) and the two accepted input forms. An agent knows precisely what question this answers and can distinguish it from the sibling lookups (destinations_search, plans_find), which cover different resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended usage is implied clearly: supply one device by name or model code and get a compatibility verdict. But there is no explicit when-to-use framing, no statement of when not to use it, and no named alternative for related questions (e.g. plan or destination lookups). Guidance is adequate but inferred rather than stated.

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