Skip to main content
Glama

Check whether a phone supports eSIM

check_device
Read-only

Use this before recommending a purchase when it is not certain the traveller's phone takes an eSIM, e.g. "does my iPhone 13 work?", "Galaxy A54 eSIM?". Returns GlobalPass's compatibility note for the model family and the check that settles it on the phone itself (an EID line in the settings).

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": "check_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesThe phone model, e.g. "iPhone 14 Pro", "Pixel 8".
languageNoLanguage of the answer: en, pl or ru.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 genuine value by disclosing what is returned (a model-family compatibility note plus the on-device EID check) rather than leaving the response shape opaque. It does not say how unknown or unsupported models are handled, which is the main remaining behavioral gap.

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?

It is front-loaded with the usage trigger, then the return contract, in two tight clauses with no filler. The example queries are compact and help ground the intent rather than padding the text.

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 only two simple parameters and no output schema, the description does enough: it explains the purpose, the trigger, and what comes back. The missing piece is edge-case behavior for unrecognized or eSIM-incapable models, which matters for a lookup tool that will inevitably receive mismatched model strings.

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 both the model string and the language enum are already documented in the schema; the description only echoes model examples that the schema itself supplies. It adds no guidance on the language parameter's effect on the answer, 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?

The description names a specific check (whether a phone model supports eSIM) and states both the input framing (phone model family) and the two things returned: GlobalPass's compatibility note plus the on-device EID verification. This is clearly distinguishable from the sibling tools (get_faq, plan_trip, search_plans), none of which perform device compatibility checks.

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: use it before recommending a purchase when it is not certain the traveller's phone takes an eSIM, reinforced by example user phrasings. It does not state when not to use it or name an alternative route for cases where certainty already exists, so it stops short of full routing guidance.

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