Skip to main content
Glama

Diameter AVP detail

diameter_avps
Read-onlyIdempotent

Extract and inspect Diameter request and answer AVPs by session, subscriber, command code, or frame, returning key result fields or a full nested AVP tree.

Instructions

The AVPs of Diameter requests and answers, paired as in diameter_transactions. Select with session_id, imsi (User-Name digits), command_code (316 ULR, 317 CLR, 318 AIR, 319 IDR, 321 PUR, 272 CCR, ...) and/or frame (a request or answer frame number); the whole session is fetched so answers are kept. detail="key" (default) gives the AVPs read first: Result-Code and Experimental-Result, ULR/ULA/CLR/PUR/PUA/ IDR/NOR flags with bit names, Cancellation-Type, RAT-Type, Visited-PLMN-Id, AIR vectors, Gx CC-Request-Type, Event-Trigger, rule reports and QoS, and a digest of Subscription-Data (MSISDN, status, ODB, access restrictions, AMBR, one line per APN with PDN type, QCI, ARP, AMBR and PGW), plus a per-application digest under gy, rx, cx, sh or s13 whose failed codes carry cause_lookup's explained. detail="full" gives every AVP as a nested tree, at most max_avps leaf AVPs per message (server cap 2000); avps_dropped counts the rest. Authentication material is never returned. limit caps transactions (default 20). filter is ANDed with diameter. More detail: resource schema://tools/diameter_avps.

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": "diameter_avps"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoSame forms as start
imsiNoIMSI, 6 to 15 digits
pathYesCapture file (absolute, in an allowed dir) or open_capture handle
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_avpsNoMost AVPs per message
session_idNoDiameter Session-Id
command_codeNoDiameter command code, such as 316 (ULR) or 272 (CCR)
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, request, answer, command, application, session_id, user_name, origin_host, destination_host, answer_origin_host, request_frame, answer_frame, rtt_ms, result, success, unanswered, unmatched_answer, request_avps, answer_avps, request_avps_dropped, answer_avps_dropped
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.2/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses several non-obvious behaviors: whole-session retrieval when a frame is selected, that authentication material is never returned, a server cap of 2000 AVPs, `avps_dropped` counting truncated AVPs, `limit` defaulting to 20, and `filter` being ANDed. These are exactly the traits an agent could not infer from 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?

Purpose and selectors are front-loaded, then the two detail modes and caps, which is a sensible order. The long parenthetical enumerations of AVPs and digest fields make sentences dense and slightly scannable-resistant, but nearly every item earns its place as content documentation.

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, return-value documentation is not required, and the description still covers selection, detail modes, truncation, and filtering for a 16-parameter tool. It leaves `redact`, `output`/`max_output_kb`, and the required `path` handle entirely to the schema, which is acceptable but the only remaining 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 3 is the floor, but the description adds real meaning: `imsi` is clarified as User-Name digits, `command_code` values are named (316 ULR, 272 CCR, ...), `frame` accepts a request or answer frame, `max_avps` interacts with a 2000 server cap, and `detail` values are given concrete content. It does not touch `redact`, `columns`, `output`, or `start`/`end`, which the schema carries alone.

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 opening sentence names the resource precisely ("The AVPs of Diameter requests and answers") and anchors it to a sibling ("paired as in diameter_transactions"), so an agent can tell it apart from transaction-level and packet-level tools. The action is implied rather than stated with an explicit verb like 'extract' or 'list'.

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?

It enumerates the selectors that scope a call (`session_id`, `imsi`, `command_code`, `frame`) and explains the important behavior that selecting one message still fetches the whole session 'so answers are kept'. It also gives clear guidance between `detail="key"` and `detail="full"`. It does not state when to prefer this over `packet_detail` or `diameter_transactions`, but that is a minor gap.

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