Skip to main content
Glama

Device compatibility guidance

check_device_compatibility
Read-only

Looks up a phone or cellular tablet in Horizon's curated eSIM device list. A listed model is not proof that every regional variant is compatible or carrier-unlocked, and not_listed does not mean incompatible. Matching is most reliable with the exact model name and the region where the device was sold. The lookup needs no IMEI or EID.

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

Input Schema

NameRequiredDescriptionDefault
modelYes

Output Schema

NameRequiredDescriptionDefault
urlYes
matchYes
checksYes
modelsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint false), so the description's added value is in result interpretation: a listed model does not guarantee every regional variant or carrier-unlock, and not_listed is explicitly not proof of incompatibility. That pre-empts the two most likely misreadings of the output, which is meaningful context beyond structured fields.

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?

Four sentences, front-loaded with the purpose and then the caveats; each sentence addresses a distinct agent question (what it does, how to read 'listed', what to pass, what not to pass). Slight cost for the misleading region mention, which introduces rather than resolves uncertainty.

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?

An output schema exists, so return-format detail is unnecessary, and the tool is a single read-only lookup with one required string; the prerequisites ('no IMEI or EID') and result caveats make it nearly self-sufficient. The only gap is the unresolved role of region in matching.

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 coverage is 0% for the single 'model' parameter (only minLength/maxLength constraints), so the description carries the burden and does add real meaning about using the exact model name. However, it refers to 'the region where the device was sold' even though no region parameter exists, leaving the agent unsure whether region belongs inside the model string or cannot be supplied at all.

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 — 'Looks up a phone or cellular tablet in Horizon's curated eSIM device list' — which is unmistakably distinct from the destination/plan/support siblings. The scoping to eSIM devices plus the curated-list framing lets an agent route here without ambiguity.

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?

The description makes clear when the answer is trustworthy ('matching is most reliable with the exact model name and the region where the device was sold') and what inputs are NOT required ('needs no IMEI or EID'), which usefully excludes a plausible wrong path. It does not explicitly name a sibling alternative or state an exclusion condition, so it falls short of full when/when-not 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