Skip to main content
Glama

Check if a phone supports eSIM

check_phone_esim_support
Read-onlyIdempotent

Whether a phone model supports eSIM: "iPhone 13", "Galaxy S23", "Pixel 7a", or an Android model code such as "SM-S911B". Returns supported, not_supported or unknown.

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_phone_esim_support"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesPhone model name or code.

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, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds real value beyond that by disclosing the three possible outcomes (supported, not_supported, unknown), signaling that an indeterminate result is possible rather than a binary 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 tight sentence front-loads the purpose, embeds input format examples, and closes with the return values. No wasted wording.

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, read-only lookup with no output schema, the description covers purpose, input formats, and result values. It stops short of explaining when 'unknown' occurs or how matching/normalization works, a minor but real gap.

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

Parameters4/5

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

Schema coverage is 100%, so baseline would be 3, but the description earns above that by illustrating the accepted input formats: marketing names like 'iPhone 13' or an Android model code like 'SM-S911B'. That is meaningfully more than the schema's bare 'Phone model name or code.'

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 names a specific verb and resource ('Whether a phone model supports eSIM') and gives concrete example inputs. Sibling tools (find_esim_plans, list_esim_destinations, estimate_trip_data) are clearly different operations, though the description never explicitly says so.

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?

Usage is only implied: the agent can infer this is a device-compatibility lookup rather than a plan or destination lookup. There is no explicit statement of when to call this versus checking plans, and no prerequisites or exclusions are given.

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