Skip to main content
Glama

GTPv2-C information elements

gtp_ies
Read-onlyIdempotent

Extracts information elements from paired GTPv2-C requests and responses in packet captures, filtered by IMSI, TEID, frame, or message, with key or full IE detail and likely cause hints.

Instructions

The information elements of paired GTPv2-C requests and responses: the GTP counterpart of diameter_avps. Select with imsi, teid (header or F-TEID, decimal or 0x hex), frame (a request or response frame) and/or message (type number or name, e.g. "Create Session Request"; a request name also selects its response); both halves of each transaction are kept. detail="key" (default) gives request_ies and response_ies with the IEs read first: IMSI, MSISDN, MEI, APN, selection mode, PDN type, PAA, APN restriction, serving network, RAT, ULI (TAI, ECGI, CGI, SAI, RAI with MCC-MNC), UE time zone, indication flags set, charging characteristics and ID, recovery, APN-AMBR, F-TEIDs by interface, PCO option names (never PAP/CHAP contents), bearer contexts (EBI, QCI, ARP, MBR/GBR, F-TEIDs, cause), the cause with its offending_ie and source (CS bit), and the RAN/NAS cause a Delete Session carries; other IEs are listed by name. A rejected or partly accepted response adds likely_causes built from the request (cause 78 and the APN sent, 73 with IPv4v6 requested, 92 with PAP in the PCO, 64 and the Recovery IE, ...). detail="full" gives every IE as a tree, at most max_ies IEs per message (server cap 2000). filter is ANDed with gtpv2; limit caps transactions (default 20).

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>"
    },
    "name": "gtp_ies"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoSame forms as start
imsiNoIMSI, 6 to 15 digits
pathYesCapture file (absolute, in an allowed dir) or open_capture handle
teidNoGTP TEID: an int or hex string such as 0xc001
frameNoFrame number
limitNoMost rows per page
startNoISO 8601, epoch s, +Ns from start, -Ns from end
detailNokey (the AVPs or IEs that explain a result) or fullkey
filterNoExtra display filter, ANDed
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)
max_iesNoMost IEs per message
messageNoGTPv2-C message name or type number, such as Create Session Request or 32
max_output_kbNoLower output cap, KB

Output Schema

NameRequiredDescriptionDefault
countNo
errorNo
detailNo
offsetNo
windowNo
droppedNo
has_moreNo
returnedNo
selectionNo
next_offsetNo
total_foundNo
transactionsNorows with keys: time, message, response, seq, teid, request_frame, answer_frame, rtt_ms, cause, cause_name, accepted, unanswered, request_ies, response_ies, request_ies_dropped, response_ies_dropped, likely_causes
total_matchedNo
packets_matchedNo
packets_scannedNo
total_is_lower_boundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial behavior: what `detail="key"` returns versus the full tree, the server cap of 2000 IEs, the `likely_causes` inference built from the request for rejected responses (cause 78/73/92/64), and the privacy guarantee that PCO option names are shown but never PAP/CHAP contents. This is context an agent could not get from annotations or schema.

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?

Front-loaded with what the tool is and how to select, then detail modes, then limits – a logical order with little waste. The long enumeration of IEs shown at `detail="key"` is dense but functional, telling the agent exactly what it will get; it could be tightened slightly without losing meaning.

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 16-parameter tool with an output schema, the description covers selection, detail levels, caps, and privacy of PCO contents well. Notable gaps remain: `redact` (a subscriber-identifier safety switch) and `output="summary"`/`offset` pagination are never mentioned.

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?

With 100% schema coverage the baseline is 3, and the description earns above that: it explains that `teid` may be header or F-TEID in decimal or 0x hex, that `message` accepts a type number or name and a request name also selects its response, that `max_ies` is capped at 2000 server-side, and that `filter` is ANDed with `gtpv2`. Undocumented here are `redact`, `columns`, `output`, and pagination via `offset`/`start`/`end`.

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 resource (GTPv2-C information elements from paired requests/responses) and explicitly anchors it to a known sibling: 'the GTP counterpart of diameter_avps'. It also implicitly separates itself from gtp_sessions by noting `filter` is ANDed with `gtpv2`. An agent can identify the tool without opening the schema.

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?

Gives clear selection guidance: combine `imsi`, `teid`, `frame`, `message`, with the useful rule that a request name also selects its response, plus default `limit` and detail levels. It lacks an explicit routing statement such as when to prefer gtp_sessions over gtp_ies, so it stops 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.