Skip to main content
Glama

Diameter transactions

diameter_transactions
Read-onlyIdempotent

Pair Diameter requests with their answers, showing command, result code, round-trip time, and unanswered requests so you can spot failures and slow responses in a capture.

Instructions

Pair Diameter requests with their answers (Hop-by-Hop + End-to-End id, checked against Session-Id). Use it for which requests failed or went unanswered and how slow the answers were; group them per Session-Id with diameter_sessions, read the AVPs behind a transaction with diameter_avps, follow one subscriber across protocols with trace_subscriber. Each transaction gives command code and name (ULR/ULA, AIR/AIA, CCR/CCA, ...), application, origin/destination host and realm, User-Name (IMSI), Result-Code or Experimental-Result-Code with its name, round-trip ms and unanswered: true for requests with no answer. An unanswered request whose capture stops before its answer was due (the last packet on its interface comes before the slowest answer to the same command in the capture plus 0.2 s, at most 2 s) also gets near_capture_end and a note; summary.unanswered_near_capture_end counts those. filter is an optional display filter ANDed with diameter, e.g. diameter.cmd.code == 316.

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

Input Schema

NameRequiredDescriptionDefault
endNoSame forms as start
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
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_output_kbNoLower output cap, KB

Output Schema

NameRequiredDescriptionDefault
countNo
errorNo
offsetNo
windowNo
droppedNo
summaryNokeys: by_message, unanswered, failed, legs_without_response, legs_near_capture_end, unanswered_near_capture_end, duplicates
has_moreNo
returnedNo
next_offsetNo
total_foundNo
transactionsNorows with keys: time, src, dst, request_frame, answer_frame, rtt_ms, unanswered, unmatched_answer, leg_without_response, near_capture_end, duplicate_of_frame, chain, note, command_code, command, request, answer, application_id, application, session_id, hop_by_hop, end_to_end, origin_host, origin_realm, destination_host, destination_realm, user_name, retransmitted, answer_origin_host, result_code, experimental_result_code, result, mscc_result_codes, mscc_results, success, error_bit
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.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses the returned fields, the `unanswered: true` marker, and the non-obvious `near_capture_end` heuristic with its exact timing rule (slowest same-command answer + 0.2 s, capped at 2 s) plus the summary counter. That heuristic is genuinely valuable behavioral context an agent could not infer. It stops short of describing pagination behavior, which keeps it from 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.

Conciseness4/5

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

Front-loaded with the core purpose and the routing sentence before the field inventory. It is dense and long, but nearly every clause carries information (field list, heuristic, filter example). The field enumeration is slightly list-like but justified for a transaction tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter, output-schema-bearing tool, the description covers purpose, alternatives, returned fields, the tricky unanswered/near-capture-end semantics, and filter usage. Nothing an agent needs to call it correctly is missing.

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 the baseline is 3, but the description adds real meaning for `filter`: it is ANDed with `diameter` and an example (`diameter.cmd.code == 316`) is given, which the schema does not show. Other parameters (start/end/limit/offset/redact/columns) are left to the schema, which is adequate.

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 ('Pair Diameter requests with their answers') and immediately scopes it with the matching keys (Hop-by-Hop + End-to-End id, Session-Id). It is clearly distinguishable from diameter_sessions and diameter_avps, which it names as different views of the same data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says what to use it for ('which requests failed or went unanswered and how slow the answers were') and routes to alternatives with their purposes: diameter_sessions for per-session grouping, diameter_avps for AVP detail, trace_subscriber for cross-protocol following. When-to-use and when-to-use-something-else are both covered.

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