Skip to main content
Glama

Roaming attach check

roaming_attach_check
Read-onlyIdempotent

Diagnose why a roaming subscriber fails to attach or obtain a bearer by grouping attach and PDN steps into timed attempts and checking subscription, routing, and access restrictions.

Instructions

Why can this roamer not attach or get a bearer. Collects the subscriber's attach and PDN steps (S6a AIR/AIA and ULR/ULA, MAP sendAuthenticationInfo, updateLocation and updateGprsLocation for 2G/3G, GTPv2-C Create Session and Modify Bearer, Gx CCR-I/CCA-I, PFCP Session Establishment) and groups them into attempts in time order. Each attempt gives visited_plmn (ULR Visited-PLMN-Id, GTPv2 Serving Network or the MAP peer GT), roaming, access (RAT, TAI, ECGI), steps with result, code, ref and frames, the ULA subscription digest (carried from an earlier attempt when this one has no ULA), the Create Session request (APN, PDN type, selection mode, RAT, serving network, flags, APN-AMBR), checks (APN subscribed, PDN type allowed, home routing or local breakout from the APN operator identifier against VPLMN-Dynamic-Address-Allowed, RAT against Access-Restriction-Data, ODB, AMBR), first_failure and a one-sentence verdict. home_plmn ("MCC-MNC") overrides the home network read from the IMSI (needed for multi-IMSI SIMs and MVNO ranges; otherwise the MNC length follows the MCC). Content-free: no authentication vectors, SMS or USSD text are read or returned.

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": {
      "path": "<path>",
      "imsi": "<imsi>"
    },
    "name": "roaming_attach_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoSame forms as start
imsiYesIMSI, 6 to 15 digits
pathYesCapture file (absolute, in an allowed dir) or open_capture handle
limitNoMost rows per page
startNoISO 8601, epoch s, +Ns from start, -Ns from end
msisdnNoMSISDN (E.164 digits, no +)
offsetNoRows to skip (next_offset)
outputNosummary: all but rows, plus 3 rows (<8 KB)rows
redactNoReplace subscriber identifiers in this result with tokens; ids+ips hides every IP toooff
columnsNoRow keys to keep (frame keys stay)
home_plmnNoHome PLMN as MCC-MNC, such as 001-01 (default: from the IMSI)
max_output_kbNoLower output cap, KB

Output Schema

NameRequiredDescriptionDefault
imsiNo
countNo
errorNo
offsetNo
passesNo
windowNo
droppedNo
summaryNo
verdictNo
attemptsNorows with keys: time, visited_plmn, visited_source, roaming, access, steps, subscription, subscription_frame, subscription_from_earlier_attempt, request, checks, first_failure, verdict
has_moreNo
returnedNo
home_plmnNo
next_offsetNo
total_foundNo
total_matchedNo
packets_matchedNo
packets_scannedNo
home_plmn_sourceNo
total_is_lower_boundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world, so the bar is lower, but the description still adds real disclosure: it is explicitly content-free (no auth vectors, SMS or USSD text read or returned) and spells out which interfaces feed the result. It does not cover cost/performance of a full multi-interface correlation or how paging behaves across `attempts`, which keeps it off a 5.

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

Conciseness3/5

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

The purpose question is correctly front-loaded, but the body is a single dense paragraph that spends the majority of its length enumerating returned fields (`attempts`, `visited_plmn`, `checks`, `first_failure`, `verdict`) that an output schema already carries. The technical density is justified for the domain, yet a chunk of the text does not earn its place against structured data.

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 high-complexity correlation tool it conveys the interfaces mined, the output shape, the override parameter, and a privacy guarantee, which is enough for an agent to call it confidently; an output schema exists so return values need no further explanation. Minor gaps remain around result ordering across captures and paging/offset interaction, but nothing critical is missing.

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 the schema already documents all 12 parameters and the baseline is 3. The description does add genuine meaning for `home_plmn` (the IMSI-derived default, why multi-IMSI SIMs and MVNO ranges need the override, and the MCC-driven MNC length rule), but it says nothing about `redact`, `output`, `columns` or window semantics, so the lift is modest.

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?

Opens with the exact diagnostic question ('Why can this roamer not attach or get a bearer') and then names the concrete resource it assembles: S6a AIR/AIA, ULR/ULA, MAP auth/location, GTPv2-C session/bearer, Gx CCR-I, PFCP establishment, grouped into ordered `attempts`. This is a specific verb+resource+scope that no sibling (e.g. diameter_sessions, gtp_sessions, ims_registration) covers in the same correlated form.

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 failure scenario is implied strongly by the opening question, so an agent can infer when to reach for it, but there is no explicit when-not guidance and no sibling is named as an alternative (e.g. for pure single-protocol lookups use diameter_transactions or gtp_sessions). Usage is implied rather than directed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.