Skip to main content
Glama

eSIM troubleshooting steps

get_troubleshooting_steps
Read-only

Returns Horizon's approved steps for one eSIM problem, in the customer's language and in the order to try them: the eSIM does not install, no signal, signal but no internet, slow data, or the hotspot does not work. None of the steps deletes the eSIM.

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": {
      "issue": "<issue>"
    },
    "name": "get_troubleshooting_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueYesinstall: the eSIM does not install. signal: no signal. internet: signal but no internet. slow: the connection is slow. hotspot: the hotspot does not work.
localeNoThe customer's language code, one of en, sq, de, tr, fr, ar, pl, es, ru, hr, it, zh, he, ja, af. Other codes get English.
platformNoThe customer's phone: ios for an iPhone, android for an Android phone, unknown when the customer did not say.unknown

Output Schema

NameRequiredDescriptionDefault
issueYes
stepsYes
localeYes
platformYes
issueLabelYes
completedTextYes

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 and destructiveHint=false, so the safety profile is covered; the description still adds domain-specific reassurance that 'none of the steps deletes the eSIM' and, more usefully, discloses that steps come back in the order to try them. It does not discuss what happens when no steps exist for a platform, which is the only meaningful 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?

Two sentences, front-loaded with what is returned before the enumeration of issues. The list of five problems duplicates the schema enum, which is mild redundancy but keeps the definition readable in isolation.

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 an output schema present and annotations covering the safety profile, the description only needs to frame the purpose and result shape, which it does. The notable omission is any mention of the platform parameter, which presumably tailors the steps per OS and is left entirely to the schema.

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 both enums are documented, so the baseline is 3. The description largely echoes the schema — the five issue categories restate the issue enum and 'in the customer's language' restates locale — and it never mentions the platform parameter or how it changes the returned steps.

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 ('Returns Horizon's approved steps for one eSIM problem'), scopes it to a single issue, and enumerates the five problem categories covered. No sibling tool in the catalog touches troubleshooting steps, so the domain alone separates it from get_support_policy or check_device_compatibility.

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 scope is clear: it applies when a customer has one of the five listed eSIM problems. There is no explicit when-not guidance or routing advice (e.g., whether to run check_device_compatibility first), so the agent must infer sequencing from context.

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